>On the other side creating native threads is an expensive operation.
>Especially on Linux, where threads are heavy-weight system processes.
Can anyone tell me whether the Linux port of native threads uses some
sort of thread reuse mechanism to cut down on the OS overhead? Ie: if
I fire up a new thread, then it stops, and then I fire up a second new
thread, does Linux/Java reuse the kernel thread from the first case?
In my current research I'm firing off threads left and right, without
any sort of pooling. The performance is OK with green_threads, but I
haven't tried it out with native. I'd really prefer not to have to
write my own thread pooling; my feeling is that this is something the
VM can do better.
[EMAIL PROTECTED]
. . . . . . . . http://www.media.mit.edu/~nelson/
