4 ms·

Maybe it's a workaround for the issue where HN hugs itself to death if comments get over a certain number.

noir_lord 10y ago
If that's the case and given all the recent issues (including the somewhat hilarious "Can you all log out because S3 falling over is killing us EDIT: for clarity - Because of the level of auth'd user activity not because HN depended on S3" stuff) maybe it is time they actually considered fixing HN.
- positr0n 10y ago
  I've seen the mods make the "please log out to save load on our server" announcement a few times on really busy threads. My understanding is it wasn't because HN depends on S3 but because everyone was on HN at the same time talking about it! Edit: my google/HN Search fu is failing to find a reference, but they can't easily horizontally scale HN because it is running on a single arc process. Comments/Submissions are stored in text files, and the "More" links are actually stored in memory in closures. When the closures get garbage collected you get the "Unknown or expired link." error.
  - noir_lord 10y ago
    Yeah I wasn't very clear about that I edited. It was the volume of comments in a single thread.
  - deleted 10y ago
    [deleted]
  - foxylion 10y ago
    I'm really curious why the backend is in that state since so long. Today everything is scalable but HN performance is limited to a single process? And the complexity shouldn't be too high to migrate it to another framework/... when the current one does by design not support a multi process architecture. Do I miss something?
- jafingi 10y ago
  The reason why that's happening is because when you're logged in, they can no longer server your response from the cache. So they have to render the page for _you_.
  - noir_lord 10y ago
    I know the reason why, it doesn't negate my point that given they are having so many issues recently (or possibly blind chance has made me see them having so many issues) it might be time to consider updating it.

If that's the case and given all the recent issues (including the somewhat hilarious "Can you all log out because S3 falling over is killing us EDIT: for clarity - Because of the level of auth'd user activity not because HN depended on S3" stuff) maybe it is time they actually considered fixing HN.

positr0n 10y ago
I've seen the mods make the "please log out to save load on our server" announcement a few times on really busy threads. My understanding is it wasn't because HN depends on S3 but because everyone was on HN at the same time talking about it! Edit: my google/HN Search fu is failing to find a reference, but they can't easily horizontally scale HN because it is running on a single arc process. Comments/Submissions are stored in text files, and the "More" links are actually stored in memory in closures. When the closures get garbage collected you get the "Unknown or expired link." error.
- noir_lord 10y ago
  Yeah I wasn't very clear about that I edited. It was the volume of comments in a single thread.
- deleted 10y ago
  [deleted]
- foxylion 10y ago
  I'm really curious why the backend is in that state since so long. Today everything is scalable but HN performance is limited to a single process? And the complexity shouldn't be too high to migrate it to another framework/... when the current one does by design not support a multi process architecture. Do I miss something?
jafingi 10y ago
The reason why that's happening is because when you're logged in, they can no longer server your response from the cache. So they have to render the page for _you_.
- noir_lord 10y ago
  I know the reason why, it doesn't negate my point that given they are having so many issues recently (or possibly blind chance has made me see them having so many issues) it might be time to consider updating it.