4 ms·

The traffic killed the server - I'm rebuilding it now with decent RAM, back in 20 minutes..

• cr3ative 12y ago
  I have to admit I giggled http://i.imgur.com/H9dBG09.png http://i.imgur.com/H9dBG09.png Hope the rebuild goes well.
  • stevekemp 12y ago
    Redeploying is pretty automated, but it looks like I need significant caching on the front-end to cope with load.
    • eli 12y ago
      I'm a huge fan of Varnish for this sort of thing.
• Retr0spectrum 12y ago
  Out of curiosity, what are the specs of the server, and how much RAM is "decent"?
  • stevekemp 12y ago
    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.
    • ten7 12y ago
      Why not just slap Varnish in front of that and be done?
      • stevekemp 12y ago
        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.
        • latchkey 12y ago
          Which brings the next question... why not use Github for authentication?
        • X-Istence 12y ago
          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.
    • opless 12y ago
      Perl/CGI is never a good thing. You might get better response with using perl in fastcgi mode, and using nginx rather than apache.