Re: Multiple issues in Squid-3.2.3 SMP + rock + aufs + a bit of load

mån 2012-12-03 klockan 23:12 -0700 skrev Alex Rousskov:

> BTW, once zero-delay events are removed from the code, the event queue
> will no longer need to be a part of the wasActivity loop and the loop
> will disappear.

Note: Legacy zero-delay addEvent events are meant to be called once per
comm loop. Not immediately/chained. This is by design.

The fact that zero (or shorter than current workload) delay addEvent
events gets called immediately before next comm event check is a bug
introduced with the AsyncCall merge when the discussed sawActivity
event-loop-in-the-event-loop was added.

heavy events in the context of addEvent events are really "this is very
heavy", and there is only allowed to be one and only one heavy event per
comm invocation. If there is multiple heavy jobs competing for time they
are meant to get scheduled in a round-robin fashion with comm inbetween
each.

Regards
Henrik
Received on Tue Dec 04 2012 - 08:59:14 MST