Making a site that can handle #1 on Hacker News
blog.appraptor.com
Making a site that can handle #1 on Hacker News
1–10 of 48 posts
Re: Making a site that can handle #1 on Hacker News
#2Yep, static is the way to go if that's all you need. I didn't even hit #1 on HN but got 5,000+ page views in a few hours. All on a 128MB RAM VPS:http://linuxterm.com/static-sites-for-fun-and-savings.html
Re: Making a site that can handle #1 on Hacker News
#3Yep, static is the way to go if that's all you need. I didn't even hit #1 on HN but got 5,000+ page views in a few hours. All on a 128MB RAM VPS: http://linuxterm.com/static-sites-for-fun-and-savings.html
Yep! I moved my blog over to Github pages which is just using Jekyll and it's been great. You can also pull in various JS widgets to add comments, etc.
Re: Making a site that can handle #1 on Hacker News
#4A lot of people commented on the original submission in which he asked for feedback on his site and ... nothing's improved, not even the grammatical errors!
The only thing that's changed is the site's migration to S3 from Linode, and the addition of Cloudfront!
Re: Making a site that can handle #1 on Hacker News
#5A lot of people commented on the original submission in which he asked for feedback on his site and ... nothing's improved, not even the grammatical errors! The only thing that's changed is the site's migration to S3 from Linode, and the addition of Cloudfront!
I beg to differ. I changed a lot of stuff which was recommended by HN. What errors do you see? The main thing I didn't change was I kept the open source stuff highlighted because the vast majority of people visiting the site will want to find those resources.
Re: Making a site that can handle #1 on Hacker News
#6A lot of people commented on the original submission in which he asked for feedback on his site and ... nothing's improved, not even the grammatical errors! The only thing that's changed is the site's migration to S3 from Linode, and the addition of Cloudfront!
Also, it's unreasonable to expect the author to make every change which is recommended. Some things are judgement calls. I really appreciated the feedback of HN and acted on most things suggested, but not everything.
Re: Making a site that can handle #1 on Hacker News
#7Another method, if you decide against a statically generated site, is microcaching [1] with nginx. Your backend only needs to render the page once each second and subsequent requests see the cached version. You should be able to easily handle 2000 req/s using this method.
[1] http://fennb.com/microcaching-speed-your-app-up-250x-with-no...
Re: Making a site that can handle #1 on Hacker News
#8A lot of people commented on the original submission in which he asked for feedback on his site and ... nothing's improved, not even the grammatical errors! The only thing that's changed is the site's migration to S3 from Linode, and the addition of Cloudfront!
I beg to differ. I changed a lot of stuff which was recommended by HN. What errors do you see? The main thing I didn't change was I kept the open source stuff highlighted because the vast majority of people visiting the site will want to find those resources.
"Get Perks at Local Restaurants & Bars" shouldn't be title cased. It should be "early beta" not "early Beta". The ellipsis after the "etc" should be a period. There are many others too.
There were a ton of comments that were incredibly constructive and valid. I appreciate it's your site and you're not beholden to anybody, but almost all the criticism that was given was ignored.
Also, you can edit comments on HN rather than leaving a second as an afterthought.
Re: Making a site that can handle #1 on Hacker News
#9While the sentiment is clear, I had an uncached Wordpress site on shared hosting withstand #2 or #3 (I forget where exactly it peaked). HN isn't all that huge a traffic deliverer. It's just about the quality of that traffic.
Re: Making a site that can handle #1 on Hacker News
#10While the sentiment is clear, I had an uncached Wordpress site on shared hosting withstand #2 or #3 (I forget where exactly it peaked). HN isn't all that huge a traffic deliverer. It's just about the quality of that traffic.
I agree. Vanilla Wordpress plus cache doesn't even sweat on HN traffic. I would guess that without cache it would still work.