3 ms·
It is interesting NGINX returned 502 nearly instantly under very heavy CPU load. I would have expected requests to just hang or timeout.
by nodesocket 7y ago
It is interesting NGINX returned 502 nearly instantly under very heavy CPU load. I would have expected requests to just hang or timeout.
- docapotamus 7y agoI would imagine it's tiered. The Nginx servers at the front returning the 502 probably aren't the boxes running the code
- jgrahamc 7y agoyes