As far as I can figure it is because the Windows 10 TCP stack holds onto transmitted data (including the SYN's/ACK's I'm thinking but unsure yet, not looked that detailed yet) for up to 200ms or until the buffer is full for one packet. Disabling nagle and anything else I've tried seems to make no difference. IE 11, Edge, and Chrome browsers all act the same way as well and the little Googling that I've done has not revealed an easy way to disable this 'feature' yet. However running ubuntu in hypervisor let me work around it and I was able to siege with impunity (hit my phoenix server with 60k connections to various router-points in less than a second).
On Tuesday, July 26, 2016 at 6:19:03 AM UTC-6, Scott Ribe wrote: > > On Jul 25, 2016, at 7:59 AM, OvermindDL1 <[email protected] <javascript:>> > wrote: > > > > And don't benchmark from windows either, at least on Windows 10 we've > measured the latency at ~200ms, turning off nagle, caching, everything does > not effect it. Bench from a linux VM on the same box and that 200ms > vanishes and we get 2ms latency over the internal network again... > > Interesting... The last time I wrote networking code on windows was ~20 > years ago for NT, and the networking performance was really *weird* even > then. > > -- > Scott Ribe > [email protected] <javascript:> > http://www.elevated-dev.com/ > https://www.linkedin.com/in/scottribe/ > (303) 722-0567 voice > > > > > > -- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-talk/17f52502-fbf6-46b4-928e-faacc4d81418%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
