At 09:36 PM 6/3/01 -0400, Jay Love wrote:
>We talked about this a while back, and I thought the conclusion was to do
>it. It's not very complex, anyway. But let's revive the debate....
Last time we went around on this issue, I argued that you're better off
preallocating all needed threads up front. At least on Windows NT, the
overhead of a thread that's merely blocking on a Python Queue is basically
nil. Other OS's may have worse thread implementations though -- for all of
NT's faults, it seems that threading is one thing it gets right.
I also argued that we'd be better off storing the threads on a stack
instead of a queue. That way the most recently used threads get reused,
which may produce slightly better performance. I wonder if there's a
thread-safe Stack class analogous to the Queue class that comes with Python?
Anyone else have any opinions?
--
- Geoff Talvola
[EMAIL PROTECTED]
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
