Expecting 100k hits/day burst
I'll be writing in PHP and the site itself will have relatively few functions but will have MySQL interactions.
Let me know if I can provide any further info
5 Replies
Assuming your content is reasonably cacheable, your app is reasonably well written, and your server stack is well configured, there's no reason a single 512 couldn't handle that.
If you data isn't cacheable, the app is horribly inefficient, and your server stack is badly configured, you'll be able to bring a couple of 4096's to their knees.
There are a lot of variables involved…
I don't have long to code it but it'll be efficient PHP but on a pretty much standard LAMP stack…
I think 4 req/sec is likely
Thanks for the feedback
You might want to consider using something like nginx to serve your static resources (images, css, javascript, etc), and then reverse proxy to Apache for the PHP stuff (or forget about Apache entirely and use php-fpm to run the PHP directly).
Remember to minify and gzip. Consider offloading some or all static resources entirely to a CDN like CloudFront.
If you're just serving static content, a single 512 running lighttpd/nginx/cherokee/etc could handle millions of pageviews per days. As soon as MySQL and PHP get involved, it's anybody's guess.
These are dynamic requests, delivering targetted ads to suit the host/viewer.
This is on a 2048 Linode and we have a load average of 0.08 as I type - it's not that far from idling. It's all about code optimisation.
I've been very impressed with Linode's machine performance (not to mention all the other things they're great at)