17 ms·
haha not quite, db was struggling under the load for a few minutes. b1ms postgres doesn't love 6k requests in 30 mins.
by theazureguy 5mo ago
haha not quite, db was struggling under the load for a few minutes. b1ms postgres doesn't love 6k requests in 30 mins.
- GordonS 5mo agoThose tiny b1ms VMs are absolutely pitiful (long time Azure sufferer here). It's crazy how little compute and memory Azure give you for so much money.
- theazureguy 5mo agoyeah scaling it up now, was hoping to keep costs down but HN had other ideas
- isoprophlex 5mo agoUsing azure managed PG is certainly an interesting choice if you were hoping to keep costs down
- alentodorov 5mo agotry CF. tried a version of this in feb, and it handles quite fine even under ai bot surges of 1.5m hits per day. and it’s still within the free limit btw ;) stationwatch.co.uk
- firefoxd 5mo agoA 30 second memcached/redis/etc goes a long way when sharing on HN. You go from 6k db hits to 60 hits in 30 minutes. Worked for me since 2013 [0]. [0]: https://idiallo.com/blog/handling-1-million-web-request https://idiallo.com/blog/handling-1-million-web-request
- theazureguy 5mo agoalready on it, just shipped in-memory output caching while the thread was live. next step redis if it needs it
- kaiwn 5mo agoThat’s… 3.3 r/s?