61–70 of 126 posts
Thanks for hugging my site to death! It's hosted on a $5 DO droplet and I'm honored to have this problem. https://archive.ph/AVbPV
It's a static site, no reason for the server not to be able to handle thousands of connections at once with almost no configuration changes with some like Nginx or Apache. Or even a domain which points directly to a S3 bucket. Hope you're not looking at devop roles on who is hiring posts.
A reminder that all Hacker News posts and comments are available on BigQuery and can be queried for free: https://console.cloud.google.com/marketplace/details/y-combi... (the `full` table is up-to-date; ignore the others) Here's a query for a rough reproduction of what's asked in the title: WITH whoishiring_threads AS ( SELECT id FROM `bigquery-public-data.hacker_news.full` WHERE `by` = "whoishiring" AND REGEXP_CONTA…
Say by comparing with an employees official job site and the HN post role.
Earlier quoted context omitted.
Without optimization, Nginx defaults to allowing a maximum of one worker process with 512 connections and 60s timeout. 20 unique visitors per second will lead to 500 errors in less than a minute.
Are you assuming each request takes a second, or how long? A blog should return fast enough that this isn't the case Edit: Yes, even WordPress. Unless there are 50 plugins, an unoptimized theme, zero caching, and a resource constrained server.
When each request is from a different person, you get essentially zero cache. Nope, server-side caching reduces back-end processing.
Earlier quoted context omitted.
It does not matter how fast the backend is. A persistent HTTP connection will last 60 seconds following the latest client request, unless the browser goes out of its way to explicitly close the connection. P.S. OP's website uses Apache but the same issue of overly conservative limits still apply.
There's no way the connection just sits idle and the worker can't serve other requests for the full timeout, right? That just sounds... Wrong. And is not consistent with load testing I've done before with a nginx setup
Meta-side question I've had since being part of this community for awhile, how come when a YC staked company posts they are hiring comments are disabled? As I post this "Generally Intelligent" (YC S17) is hiring for ML people (spot 15 per my last refresh.)
Thanks for hugging my site to death! It's hosted on a $5 DO droplet and I'm honored to have this problem. https://archive.ph/AVbPV
Looks like you have June 2021 as the all time high as well. Doesn't look like June 2022 is going to get even close, which makes sense based on current freezes/layoffs.
Earlier quoted context omitted.
Are you assuming each request takes a second, or how long? A blog should return fast enough that this isn't the case Edit: Yes, even WordPress. Unless there are 50 plugins, an unoptimized theme, zero caching, and a resource constrained server.
> zero caching When each request is from a different person, you get essentially zero cache. Nope, server-side caching reduces back-end processing.
There's fastcgi caching in nginx, php opcode in php-fpm, and WP specific cave plugins like Super Cache. At least this was the case ~10 years ago.