Adam Heath wrote:
On Thu, 16 Jan 2003, danch wrote:


It's not especially computation intensive, but it is resource intensive:
it consumes a process table entry. Each user is allowed only a certain
number of process table entries, and the overall system has an upper limit.

This latter point is no longer true, in 2.4.
Sure, you can change the parameter. However, at some point you will run out of some resource on the system. OK, maybe not from a practical point of view on the latest uber-box, but this conversation strayed from 'practical' into theoretical long ago...sorry about that.

Also, more threads will load the OS scheduler more. If they're idle it
isn't as bad as if they're active, but it will/may consume time
depending on the scheduling algorythm.

More runnable threads.  Sleeping threads come for free.




-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to