On Thu, Oct 18, 2018 at 11:05 AM, Laurent Bourgès <bourges.laur...@gmail.com
> wrote:
>
>
> There is no shame that EDT or event processing consuming lots of cpu
> cycles, in such intensive tests.
>
>
That's not a problem, the problem is starvation of
non-SequencedEvent events if the EDT is blocked-like rejecting them all.
Even though all of this is artificially caused, it's a good opportunity to
get it right and it's actually very nice that your 1st test exposed this
scenario.

Reply via email to