4 ms·
The only change I would make to the "stages" is to add caching up front. Most modern web frameworks make the use of caching pretty trivial therefor making it le
by tdavis 18y ago
The only change I would make to the "stages" is to add caching up front. Most modern web frameworks make the use of caching pretty trivial therefor making it less of a pain than setting up load balancers and multiple web servers, etc. Static content should also make use of caching headers and be served by a separate server than dynamic content; this is also a trivial improvement.
Having only a single web server, database server, and static content server while making liberal use of caching and smart querying result in benchmarks indicating we can sustain around 1900 req/sec. Even if that isn't entirely accurate, the chances of us reaching the 82 million page views per month to find out is all but inconceivable.
- litewulf 18y agoCaching is hard though, and its best to use profiling to decide what to cache. Especially if you have any sort of user-specific content, you need to resort to fragment caching which is sometimes tricky.
- alecco 18y ago1900 req/sec What kind of requests? Typically dynamic content usually is well below 300 req/s per core and goes down fast on many factors (e.g. non-local database.) Most web frameworks are usually below the 300 req/s mark. Of course it is a very complex subject as there are many things to consider. Good cache management, CDN, SSI, and reverse cache come to mind. About databases, it can become a problem if you do writes on the same database as locking starts to show its dangerous tentacles.