4 ms·
This is really great to see that at least some people have found my tutorial useful! It's also interesting to see how much traffic being on the front of HN sen
by AlchemistCamp 7y ago
This is really great to see that at least some people have found my tutorial useful!
It's also interesting to see how much traffic being on the front of HN sends. So far it hasn't broken 200 requests in a minute (https://pbs.twimg.com/media/ECJVktXUEAE9kVN?format=jpg&name=small https://pbs.twimg.com/media/ECJVktXUEAE9kVN?format=jpg&name=...)
This is about 1/100th the traffic I load tested it to handle on a $5 Digital Ocean droplet (which I later upgraded to $10 due to TypeScript compilation using too much memory a different project).
Also, I completely forgot to set up any caching or any rate limiting on "articles" which are a new kind of thing on my site. Of course, it could easily be taken down with a DDOS.
But in the big scheme of things, this validates my belief that most people (including me) spend way too much time worrying about scalability in early stage projects!
- whizzkid 7y agoYou can save back your 5$/month by increasing your machine’s swap space. I did the same when more memory was only required for compiling. https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-18-04 https://www.digitalocean.com/community/tutorials/how-to-add-...
- bpicolo 7y agoanother option is to take advantage of Gitlab's shared CI runners for small side projects
- AlchemistCamp 7y agoI do use Gitlab CI/CD for most my projects! It's great. I still build on the droplet after it passes, though.
- freehunter 7y agoDoes anyone know how accurate their warning about swap space on an SSD is? I know SSDs have limited reads and writes and swapping to them obviously uses those limited reads/writes, but how much of a concern actually is it? Especially if you're only using swap during the compile/deploy step?
- whizzkid 7y agoAs soon as you hit some kind of limit it will abort the process and output the error. So you will be notified about it and it wont go unnoticed. And if you only use it during compile and deploy then you are at no risk :) (ps: bad grammar, on mobile)