[Solved] Strategies for large amount of db queries for single page request [closed]

Question

There’s no real hard limit. It will all depend on a number of factors; including the profile of your db traffic, the resources available to your db, your db architecture (replicated/distributed etc), your schema, your app design, network connectivity, your user’s expectations.

The best thing to do would be to have an idea of what your page load times should be (95% of page loads should be under 0.5 seconds or whatever) and then set up some benchmarking to check whether you are hitting those targets. As long as your app is structured with a layered approach and components are well encapsulated/separated you should be able to add performance improvement strategies such as cacheing as you need to to keep your performance where it needs to be.

Accepted Answer

There’s no real hard limit. It will all depend on a number of factors; including the profile of your db traffic, the resources available to your db, your db architecture (replicated/distributed etc), your schema, your app design, network connectivity, your user’s expectations.

The best thing to do would be to have an idea of what your page load times should be (95% of page loads should be under 0.5 seconds or whatever) and then set up some benchmarking to check whether you are hitting those targets. As long as your app is structured with a layered approach and components are well encapsulated/separated you should be able to add performance improvement strategies such as cacheing as you need to to keep your performance where it needs to be.