I see something else in your numbers about latency. I'm not sure how you are running your test, but it looks like the initial connection setup is taking a big chunk of time for sockjs. In the local version you have 0.07 seconds both for 10 requests and 100 requests. Maybe that's a typo. Or maybe all the time is sucked up by that socket startup delay and 90 requests happen in a negligible time.
More likely a typo, but look at the second test. In that case you have the first 10 requests taking 5.7 seconds (.57s/request), but according to next blast, you have 100 requests taking 23.2 seconds, so the last 90 requests only took .19s/request. The only explanation for this sequence is that there is a huge rampup time for the very first request out of the gate. This delay of a couple seconds is huge!
Comment
I see something else in your numbers about latency. I'm not sure how you are running your test, but it looks like the initial connection setup is taking a big chunk of time for sockjs. In the local version you have 0.07 seconds both for 10 requests and 100 requests. Maybe that's a typo. Or maybe all the time is sucked up by that socket startup delay and 90 requests happen in a negligible time.
More likely a typo, but look at the second test. In that case you have the first 10 requests taking 5.7 seconds (.57s/request), but according to next blast, you have 100 requests taking 23.2 seconds, so the last 90 requests only took .19s/request. The only explanation for this sequence is that there is a huge rampup time for the very first request out of the gate. This delay of a couple seconds is huge!