Adrian Chadd wrote: > On Sun, Dec 16, 2007, Tsantilas Christos wrote: > > >> Yes this is true. An AsyncCall class instanced for every async callback. > > And the comm code is going to register one of these per comm events? Yes.
> Have you benchmarked what that'll do to performance? :) Maybe has some performance penalty. But if there is a performance decrease, I do not think that it is huge. Normally creating a class is not more costly than creating a C struct and initialize it. The AsyncCall classes are very simple classes. Moreover, I believe with current design you are loosing more in performance, trying to prevent problems adding extra code for tests or workarounds. > > Robert's comm code changes in -3 did exactly this, and it trashed performance > at high throughput; hence why I started unwinding it.. > > > > Adrian > >
