15$ != 15$ per month
10 Million hits a day with Wordpress using a $15 server
101–110 of 115 posts
Re: 10 Million hits a day with Wordpress using a $15 server
#102The hallmark of Wordpress is ease of use. That's why you can spin up a blog right on their site, and they have a backend designed by Happy Cog. Wordpress is blog software for the technically illiterate. And then I take a look at this blog post that lists all the incantations necessary to scale Wordpress to reasonable scale and I wonder why anyone should do this. If you're setting up your own server, installing nginx,…
Regarding ease of use, if you are a dev, there's always toto or jekyll. Throw in disqus for commenting and you are pretty much done. Each blog is just a simple haml/erb/liquid template and git push is all you need to get a new page/blog up.
Re: 10 Million hits a day with Wordpress using a $15 server
#103FWIW: Amazon's Micro instances will burst to saturate unused CPU cycles on the host machine up to a hard-capped limit before being choked to death by the hypervisor. Had he run the Blitz test for 10 mins or more you would see the spike in traffic up, beyond what you think a Micro should sustain, and then it plummet to near 0 for a disturbingly long period of time[1]. If you are unlucky enough to have a Micro on a hos…
No problem, no offence taken :) I only picked the micro because it's cheap, and AWS let me fire one up, build the config, break it, trash it, and start again, all in rapid succession. One thing though, this configuration doesn't actually need much real CPU or disk resources - it's pretty much all memory, and as far as I know, AWS doesn't overcommit RAM. this means it should be "relatively" stable. The CPU usage is at…
EC2 may be a bit slow/clunky but at least it isn't a security nightmare like Linode.
Months after and they still haven't said what happened or what they fixed during the Bitcoin theft fiasco.
I wouldn't trust them again with ANY site (former customer).
Re: 10 Million hits a day with Wordpress using a $15 server
#104Earlier quoted context omitted.
I do wonder why W3 Total Cache or one of the other options isn't a standard feature of Wordpress.
Caching produces confusion, is my guess. You have to know it's there to realize how to fix the "oops, I made changes and they aren't showing up" issues.
Invalidation in the case of a blog is simple enough that the caching should be completely transparent.
Re: 10 Million hits a day with Wordpress using a $15 server
#105Or leverage a template cache on (insert any framework here) and get 2,000+ hits a second on a Linode, or 172,800,000 hits day.
Probably closer to 20,000 hits per second with Nginx configured correctly and if the framework doesn't impose too much overhead. Alternatively, use ESI with Varnish and the HTTP Cache spec and get 10,000+ hits per second on a relatively dynamic website (read: micro-caching).
Indeed, 1M per day may sound like a lot but it's really not that impressive.
Re: 10 Million hits a day with Wordpress using a $15 server
#106Or leverage a template cache on (insert any framework here) and get 2,000+ hits a second on a Linode, or 172,800,000 hits day.
Probably closer to 20,000 hits per second with Nginx configured correctly and if the framework doesn't impose too much overhead. Alternatively, use ESI with Varnish and the HTTP Cache spec and get 10,000+ hits per second on a relatively dynamic website (read: micro-caching).
Indeed, 1M per day may sound like a lot but it's really not that impressive.
Re: 10 Million hits a day with Wordpress using a $15 server
#107TL;DR - Vanilla ubuntu, configure firewall, install nginx, install wordpress, turn on wordpress caching, install and configure varnish.
Isn't there any kind of static generator for Wordpress? I'd expect a static wordpress + nginx would be sufficient to handle quite a serious load.
wp-super-cache. The original* and the best. Saves cached pages to html and html.gz, which allows nginx to serve them straight out (without even compressing them on every request).
* Not actually the original, but definitely the best.
Re: 10 Million hits a day with Wordpress using a $15 server
#108Earlier quoted context omitted.
No problem, no offence taken :) I only picked the micro because it's cheap, and AWS let me fire one up, build the config, break it, trash it, and start again, all in rapid succession. One thing though, this configuration doesn't actually need much real CPU or disk resources - it's pretty much all memory, and as far as I know, AWS doesn't overcommit RAM. this means it should be "relatively" stable. The CPU usage is at…
EC2 may be a bit slow/clunky but at least it isn't a security nightmare like Linode. Months after and they still haven't said what happened or what they fixed during the Bitcoin theft fiasco. I wouldn't trust them again with ANY site (former customer).
> Months after
It's March 31. slush's post was on March 1.
Re: 10 Million hits a day with Wordpress using a $15 server
#109Earlier quoted context omitted.
Caching produces confusion, is my guess. You have to know it's there to realize how to fix the "oops, I made changes and they aren't showing up" issues.
Invalidation in the case of a blog is simple enough that the caching should be completely transparent.
Should be, but Wordpress is built to accomodate everything, and a caching layer baked in by default would screw up so many plugins, half the community wouldn't know what to do with their blogs.
If it was baked in from the beginning, no problem, but there is so much plugin momentum in Wordpress now that throwing a caching layer on top of it would confuse the hell out of a lot of people who just want to write words.
Re: 10 Million hits a day with Wordpress using a $15 server
#110FWIW: Amazon's Micro instances will burst to saturate unused CPU cycles on the host machine up to a hard-capped limit before being choked to death by the hypervisor. Had he run the Blitz test for 10 mins or more you would see the spike in traffic up, beyond what you think a Micro should sustain, and then it plummet to near 0 for a disturbingly long period of time[1]. If you are unlucky enough to have a Micro on a hos…
+1 right you are about micro instances getting hammered by the hypervisor if you use too much sustained resources.
One trick that I used when I was temporarily hosting a small Clojure web app for a customer: I ran the web app using "nice" to reduce its priority. I did not do any measurements, so this is really subjective, but the app seemed to run a lot better as far as consistently getting a little bit of processor time to run.
Not so subjective: I did some Clojure development in a repl on a micro instance (because it was already set up for access to a Hbase cluster) and doing a "nice lein repl" really made development possible, if a little slow.