On Wed, 2007-08-22 at 08:02 -0400, Alan Conway wrote: > You were wondering about what data structure was growing so big? Guess > what: it's the Serializer again. The problem is not the serializer > per-se, its a fairness problem.
I think I understand a (little) more about the cause of this problem now. I only see the problem if I give the broker 1 netio thread. In this case the serializer thread can run on the other processor and in effect you get more resources devoted to I than O. when I run with 1 netio threads I don't see this problem as the I and O can run in parallel (on different sockets anyway) and the serializer competes with each of them equally. Well it's something along these lines I'm sure. Eliminating the extra thread of the serializer should help. Incidentally I don't see any significant speed up, but thats pr just the clients taking up the slack. I'm still seeing this with your latest changes BTW, so it's not wholly due to the allocations by the serializer. Andrew
