I've just checked in changes to make the C++ client lib use the new
asynch IO code for both reading and writing.

One issue I have not been able to properly establish is whether this
causes a performance regression: The perftest runs I've done are a lot
slower than at the beginning of the week, but they are with the C++
client code from before my changes in my tests as well!

So this is just a heads up that if anyone notices a further slow down
from now on with C++ client->broker tests my new asynch client code
could be to blame.

Actually there is some reason to expect it might make a difference as it
does mean that reading and writing in the client now happen in the same
thread, where before they mostly happened in different threads.

Andrew


Reply via email to