Containerum – Managed Docker Hosting • Hacker News Board

Based on Google cache results, I suspect that the page's rendered server-side, with React, and the container's really busy doing the same DOM stuff over and over. If owners are reading - I think the easiest trick to try (besides scaling up) would be to tell nginx to cache the index page (with `proxy_cache`), heavily - just don't forget to forcibly drop the cookies on `GET /` requests (for safety). The page from Google's cache looks mostly static, so that should do the trick. It would not know the logged-in state, but at least something would show up.

Re: Containerum – Managed Docker Hosting

#7

Post by Ascetik » Mon, Oct 30, 2017, 1:59 PM UTC

That Latin suffix.

Re: Containerum – Managed Docker Hosting

#8

Post by maxehmookau » Mon, Oct 30, 2017, 2:22 PM UTC

Sorry, if your hosting website can't handle a HN spike, you can't handle my traffic.

Re: Containerum – Managed Docker Hosting

#9

Post by alexander_kir » Mon, Oct 30, 2017, 2:24 PM UTC

drdaeman wrote: post #6

Seems that container that serves the website hadn't auto-scaled well ;) (currently it's responding with 502 Bad Gateway) Based on Google cache results, I suspect that the page's rendered server-side, with React, and the container's really busy doing the same DOM stuff over and over. If owners are reading - I think the easiest trick to try (besides scaling up) would be to tell nginx to cache the index page (with `prox…

Thank you for your comment! Our devs are working on it

Re: Containerum – Managed Docker Hosting

#10

Post by notyourday » Mon, Oct 30, 2017, 2:30 PM UTC

See, that's what happens when "just containerize it to solve scalability" motto is applied. Containers is a technology. Technology is neither positive nor negative. It just is and it comes with upsides and downsides which need to be analyzed and addressed.