4 ms·
>Finally, the connections per second rate reaches 99k, with network latency and available CPU resources contributing to the next bottleneck. Can someone educat
by muststopmyths 8y ago
>Finally, the connections per second rate reaches 99k, with network latency and available CPU resources contributing to the next bottleneck.
Can someone educate me on what they might talking about here ?
CPU is ~45% in their final graph. I don't know what network latency means in this context though. Roundtrip for a TCP handshake ? That seems unlikely.
- dzik 8y agoIt means CPU is not saturated, so it is not the bottleneck, which means it is likely not enough Erlang processes have been started.
- Qwertystop 8y agoThe CPU graph peaks near 97% (teal line) at the time when connections-per-second are highest. Are you looking at the red? That's the version without the two patches.
- muststopmyths 8y agooh yeah, you're right. I reversed the two in my head somehow.