Hey Sergey, 2008/11/27 sergey bryukov <[EMAIL PROTECTED]>: > linux kernel 2.6.22-15-386 > wt 2.2.1 > boost-1_35 > > In the example each session prints out thread id during initiation and > destroying. It is clear that not all session has uniq TID(thread id). The > output (out.txt) are given in the attachment is for 30 session, so 30 > unique TID should be presented. All session created before time out is
I am not sure why you expect each session to have its own thread, because that would be an inherent scalability problem ? The current design on purpose does not bind a thread to a session, but uses asynchronous I/O to reuse a (currently fixed-size) pool of threads to handle requests for any number of sessions ? You should also see that during the lifetime of a session, events for it are handled not all handle by the same thread, but by anyone of the available threads. Regards, koen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
