- About Optimizer Hints
- August 12–22: Online Training (EU shift)
- Clustered Indexes Dirty Secret
- Didn’t you know?
- FOSDEM Impressions
- Finding All the Red M&Ms
- June 8–18: Online Training (US shift)
- MySQL is to SQL like ??? to NoSQL
- Non-monetary micro sponsoring
- November 11-12 in Frankfurt am Main
- Online-Training in July and August
- Oracle + PostgreSQL
- Oracle Bootcamp
- PDF Registration
- Party time
- PostgreSQL Performance Event
- Quiz Results
- SQL Server Performance Kurs in Stuttgart
- SQL Server performance training in London
- SQLite learnings from PgCon
- Shipping Terms
- Springtime for SQL
- The two top performance problems caused by ORM tools
- Top Tweets January 2013
- Training Survey
- Training and Conference Dates
- Use The Index, Luke
Performance and Scalability
This chapter is about performance and scalability of databases.
In this context, I am using the following definition for scalability:
Scalability is the ability of a system, network, or process,
to handle a growing amount of work in a capable manner
its ability to be enlarged to accommodate that growth.
You see that there are actually two definitions. The first one is about the effects of a growing load on a system and the second is about growing a system to handle more load.
The second definition enjoys much more popularity than the first one. Whenever somebody talks about scalability, it is almost always about using more hardware. Scale-up and scale-out are the respective keywords which were recently complemented by new buzzwords like web-scale.
Broadly speaking, scalability is about the performance impact of environmental changes. Hardware is just one environmental parameter that can change. This chapter covers other parameters like data volume and system load as well.