News for hackers. Stuff that matters.
Re:Show HN: GitHub-based DNS Hosting by stevekemp on Sunday June 22, 2014 @04:11PM (#7929025)
Previously it was running a reasonably heavyweight Perl/CGI front-end on 512Mb RAM.

It's now setting with 4Gb of RAM, and a load of ~40.

The single biggest issue is that the front-page either shows "marketing" or "your details", so it is dynamic and being generated on-demand.

I'll update to cache.

Re:Show HN: GitHub-based DNS Hosting by opless on Sunday June 22, 2014 @05:21PM (#7929267)
Perl/CGI is never a good thing.

You might get better response with using perl in fastcgi mode, and using nginx rather than apache.

Re:Show HN: GitHub-based DNS Hosting by ten7 on Sunday June 22, 2014 @04:16PM (#7929045)
Why not just slap Varnish in front of that and be done?
Re:Show HN: GitHub-based DNS Hosting by stevekemp on Sunday June 22, 2014 @04:51PM (#7929162)
That would be the end goal - but since all users get cookies there's not obvious "I'm anonymous" vs "I'm a signed-in-user" differentiator I can use to control whether to cache or serve live.

It'll happen, shortly, but the fastest solution was to re-deploy on a scaling platform.

Re:Show HN: GitHub-based DNS Hosting by X-Istence on Sunday June 22, 2014 @06:03PM (#7929383)
When a user is logged in, use a Vary: Cookie header, when a user is not logged in, leave that off. Set the expiration time as appropriate.
Re:Show HN: GitHub-based DNS Hosting by latchkey on Sunday June 22, 2014 @05:12PM (#7929236)
Which brings the next question... why not use Github for authentication?