Database Bottlenecks in Web Apps
This cluster centers on debates about whether databases and their queries are the primary performance bottlenecks in web applications, contrasting them with issues in code, hardware, or other components.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Is processing speed the bottleneck for databases?
No, you still have a problem in your database. Running a database smoothly with large datasets is the main performance problem for web applications. As fast as you can get with smart DB architecture, DB calls still take the bulk of the time compared to code running time.
A different perspective: If the database is the bottleneck in your web application, you have a problem in your code. :-)
Well put, the database is usually the bottleneck in web applications, not the language or code.
I guess in the end the database will be the bottleneck in many cases.
Sure... until your database is your bottleneck.
Congrats. It seems like the main bottleneck of webapps is the on-disk database. I'd say that if your app is small enough you shouldn't even start with a database, but that would be a preoptimization.
Biggest bottleneck these days are poorly written sqls and badly optimized db's. Hardware isn't really an issue anymore.
Are there really many projects where the actual web framework is the bottleneck, as opposed to the DB?
This is a solution to problem that does not exists. In database heavy apps the latency is the least of the concern. unless that architecture is not optimal in some cases to meet compliance.