Hitting a limit

Question

Hitting a limit

Closed this issue 6 years ago · 4 comments

It seems like wsstat hits an artificial 90k messages/sec on 500 connections. If i have wsstat running 4 times (in 4 terminals) at the same time, the total is something like 280k messages/sec.

Any idea why it plateus?

Answer 1 · 2017-02-16T23:31:30.000Z

Hrm, that's definitely odd.

Can you give me more information about your setup? This could be because of the fact that WSStat doesn't (yet) do multiple processes, and the asyncio loop is choking.

Answer 2 · 2018-01-26T19:11:24.000Z

@Fitblip is there a plan to make wsstat multithread?

Answer 3 · 2018-01-26T20:45:12.000Z

@ficofer - No sir, wsstat relies on python3's asyncio and concurrency primitives, which, due to the GIL is essentially the same thing as using python's threading module.

The difference is that the threading module is preemptive concurrency (i.e. no control over when context switches happen) and asyncio is cooperative concurrency (i.e. once you're done computing and waiting on a blocking event (network, file access, sleep, etc), you bow back to the main IO loop).

Does that help clarify?

Answer 4 · 2018-02-13T23:06:28.000Z

Hey folks, I'm going to close this as I don't have enough details to really do anything about it.