2 ms·
You can't compare a web server serving static content to a serving dynamically generated content that comes from a database this way. All dynamically generated
by gnaritas 19y ago
You can't compare a web server serving static content to a serving dynamically generated content that comes from a database this way. All dynamically generated database bound content no matter what language or framework you use will be orders of magnitude slower than static content.
27 requests a second is just fine and vastly more than 99% of blogs will ever need. For those very few than need more, as you say, it only takes a few plugins to install caching to get speeds that match static content serving.
27 requests a second for 24 hours is 2.3 million hits a day, very very few websites out of the millions and millions in existence, get that much traffic. Why exactly are you even worried about this? 27 requests a second is not bad performance.
- henning 19y agoIt will indeed work fine for most blogs. It's just that if anything any of your users ever creates is submitted to a popular site like Digg, it won't suffice. The job of the developer is to solve problems for the user. I think not having adequate scalability built in is slacking off on the job.
- gnaritas 19y agoNot true at all, fact is most submissions to Digg still don't generate enough traffic to matter at all. Only if your post becomes popular will it get enough traffic to matter and that is also pretty rare overall, and again easily solved by the standard caching plugin.