Currently there are two types of workloads supported:
- Web
- Telco/Realtime
- with long running transactions (scans, joins and/or large updates)
- reading and especially writing of large chunks (BLOBs) of data where an "innodb" like behavior is wanted.
- requirements on response times
- requirements on failover times
- short but many parallel request primarily on PK
The Telco workload is also suitable for many kinds of applications in for example the following domains:
- Finance,
- Online gaming
- Subscriber databases
- Session management
2 comments:
Great to see this added, Johan. It would be helpful if the differences between the two were further documented so people who prefer to tune their configs directly can read in and understand as well. :)
In many deployments, the configurator may be used but as time goes on those configs are individualized.
It's good application that business people will love it. This is a good read, worth my time spent in reading it! Thanks for sharing!
Post a Comment