First time I reached the front page I had ~250 concurrent users and increasing, then the server crashed. After that I wrote a cronjob that runs a script which automatically increases my virtual machines RAM. When I have little or no visits it uses 1GB RAM the most it went up to was 9GB RAM (increasing with 1GB at a time). It also sends me an e-mail when increasing/decreasing the RAM so I can ensure that it doesn't cr…
Is Your Site Hacker News Ready?
41–50 of 51 posts
Re: Is Your Site Hacker News Ready?
#42Earlier quoted context omitted.
Non-programmers find it much easier to log into a site, type in a text box, and click 'submit' than to run some sort of static site generator.
If you're at the stage where you're maintaining your own server anyway, it doesn't seem like too much to ask. Static websites are glorious. Much more secure, much faster to load, far fewer things that can go wrong. Cheaper, too, since they require fewer resources. And, as luck would have it, there's a perfect Hacker News thread to get one started: http://news.ycombinator.com/item?id=4857473
Re: Is Your Site Hacker News Ready?
#43Tip: if you have an image-heavy blog, don't host the images somewhere that charges extra for exceeding a network traffic limit. Getting an overage charge email was how I discovered that my fractal article full of pictures was on HN. As an aside, I found that being on Reddit can give much, much more traffic than HN.
Re: Is Your Site Hacker News Ready?
#44Earlier quoted context omitted.
Non-programmers find it much easier to log into a site, type in a text box, and click 'submit' than to run some sort of static site generator.
If you're at the stage where you're maintaining your own server anyway, it doesn't seem like too much to ask. Static websites are glorious. Much more secure, much faster to load, far fewer things that can go wrong. Cheaper, too, since they require fewer resources. And, as luck would have it, there's a perfect Hacker News thread to get one started: http://news.ycombinator.com/item?id=4857473
I use Jekyll/Octopress all the time, I totally agree, static sites are great. But non-programmers are never going to use it.
Re: Is Your Site Hacker News Ready?
#45Re: Is Your Site Hacker News Ready?
#46Earlier quoted context omitted.
You could just pop Varnish cache in front of Wordpress to do the same thing - any unauthenticated GET's will just hit Varnish, and come nowhere near Wordpress itself. That way you wouldn't need to worry about software updates.
Totally. I guess I could also use some advanced Nginx directive/plugin to do that. The hack is just something that occurred to me spontaneously, it took about 2 minutes to implement, and I didn't even have to install anything :)
https://github.com/ewanleith/Wordpress-Server-Configuration-... https://github.com/ewanleith/Wordpress-Server-Configuration-...
Basically they make nginx cache itself, which combined with this Wordpress plugin:
http://wordpress.org/extend/plugins/nginx-champuru/
Makes things very minimal, no need for even a dedicated cache :)
Re: Is Your Site Hacker News Ready?
#47Forget any other setup you've ever used, go with this for high performance WordPress
1) Nginx [set so that request to static content to completely bypass PHP]
2) PHP-FPM
3) APC [Object & Database cache]
4) W3 Total Cache or WP Super Cache
5) Varnish
There many other high performance WordPress setup you could find out there but in term of simplicity and manageability, this is the one I fancy most. The bottleneck in this setup is RAM, not PHP, WordPress or MySQL read/write operation as I've seen in many server setup.
Disclaimer : I run small operation of managed WordPress hosting called KittySensei[2]
Re: Is Your Site Hacker News Ready?
#48Earlier quoted context omitted.
Non-programmers find it much easier to log into a site, type in a text box, and click 'submit' than to run some sort of static site generator.
If you're at the stage where you're maintaining your own server anyway, it doesn't seem like too much to ask. Static websites are glorious. Much more secure, much faster to load, far fewer things that can go wrong. Cheaper, too, since they require fewer resources. And, as luck would have it, there's a perfect Hacker News thread to get one started: http://news.ycombinator.com/item?id=4857473
Then lock down your CMS at a secret, SSL-only URL.
It's about 2 lines of Ruby or PHP to ping CloudFront and request an invalidation when you change a page (which only happens rarely anyway.)
Secure, fast, dynamic, only goes down if CloudFront does.