3 ms·
Although a lot of the recommendations are great, and to me it also looks like there are specific hosting problems at play, possibly serious overcommit by the pr
by mpweiher 8y ago
Although a lot of the recommendations are great, and to me it also looks like there are specific hosting problems at play, possibly serious overcommit by the provider or some plugin problems, I do think there's a deeper issue:
> What am I missing? How can I be in so much trouble in 2019 with such a relatively modest task?
Something is not quite right with our web-platform when we have these sorts of problems, and the solutions also require quite a bit of sophistication.
As an experiment, I recently switched my http://objective.st http://objective.st site to run on Objective-Smalltalk itself on a Digital Ocean $5/month droplet (their smallest). Surprisingly made it to the HN front-page and didn't hiccup, despite an egregious memory leak on my part (fixed now).
This was reported as "blazing fast"[1], despite being a single binary hosted in Frankfurt, having no CDN support and no static files, with everything served from the embedded web-server. Heck, I haven't even hooked up gzip-compression
I don't log much, so I don't really know how much traffic it's getting. I do know that hitting it with wrk remotely I got around 1000 requests/s, locally on the same box it was around 8K. So I think there's plenty of headroom. Oh, and the logs do show continuous attempts to break in POSTing to what I presume are php vulnerabilities.
I am emphatically not saying I did something amazing or even particularly good, everything was somewhere between straightforward and egregiously simple-minded, and there were other (mostly easy) ways of accomplishing the same thing. Previously the same site was served using static files running the same code as a static site generator.
However, it does confirm my suspicion that we've path-depended ourselves into a corner.
[1] https://news.ycombinator.com/item?id=18965054 https://news.ycombinator.com/item?id=18965054