Front page! Way to go Joe!
woah- small world. didn't expect to see a familiar username on this random HN thread. thanks for making JQBX!
JQBX is amazing. IWYM forever.
Hacker News “Who is Hiring?” top-level comments over time
41–50 of 126 posts
Re: Hacker News “Who is Hiring?” top-level comments over time
#42Thanks 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
Do you serve static files? Static file server on a $5 DO droplet should handle the HN front page. There's also free tiers on many CDNs like Fastly/Cloudflare. Github Pages is also free.
Even DO has their free tier for static hosting with global CDN and DDoS mitigation:
https://www.digitalocean.com/community/tutorials/how-to-depl...
Looks like the free one has only 1GB outbound transfer which wouldn't be enough for a single hug, but the $5/month one has 40GB which might be enough for a hug with text only content.
Re: Hacker News “Who is Hiring?” top-level comments over time
#43Forgetting which bit of macroeconomics this comes from, but the labor market is one of the slowest to settle (i.e. find equilibrium). Capital (real estate/manufacturing investments, stuff used to make stuff) are the slowest. So the capital unemployment rate should generally be greater than the unemployment rate, for instance.
The anecdote of Tesla posting a bunch of jobs just before the 10% reduction was announced comes to mind. Lagging indicator stuff.
Re: Hacker News “Who is Hiring?” top-level comments over time
#44Earlier 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.
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.
Re: Hacker News “Who is Hiring?” top-level comments over time
#45Forgetting which bit of macroeconomics this comes from, but the labor market is one of the slowest to settle (i.e. find equilibrium). Capital (real estate/manufacturing investments, stuff used to make stuff) are the slowest. So the capital unemployment rate should generally be greater than the unemployment rate, for instance. The anecdote of Tesla posting a bunch of jobs just before the 10% reduction was announced co…
I find it matters a lot with what sort of tech work you're doing. If you are operations, a big company needs to keep their current stuff up and running. Exploratory new programs shrivel up when things get tight, though.
Re: Hacker News “Who is Hiring?” top-level comments over time
#46Another way to interpret these results is that HN has gotten more popular as a place to source talent. It would be interesting to see top-level comments by number of total users on the site (as a proxy for popularity).
Re: Hacker News “Who is Hiring?” top-level comments over time
#47Can we overlay this with the nasdaq or some other stock index/other economic indicators?
Ask and you shall receive
https://i.imgur.com/fN5EoIB.png
Re: Hacker News “Who is Hiring?” top-level comments over time
#48Thanks 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.
Re: Hacker News “Who is Hiring?” top-level comments over time
#49Earlier quoted context omitted.
Even without optimization. Peak HN traffic is in the 20 req per second order of magnitude
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 sure? My understanding was that nginx would fill up all free connections up to the max, but then would begin draining idle connections so it could create new ones for new visitors.
Re: Hacker News “Who is Hiring?” top-level comments over time
#50Earlier 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.
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.
I can’t imagine a case where the browser wouldn’t do the decency of closing a connection.