tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28914] - add a thread pool property to set thread priority for tuning quality of service
Date Wed, 12 May 2004 02:20:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28914>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28914

add a thread pool property to set thread priority for tuning quality of service

quartz12h@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
          Component|Connector:Coyote            |Catalina
           Priority|Other                       |Medium
         Resolution|WONTFIX                     |



------- Additional Comments From quartz12h@yahoo.com  2004-05-12 02:20 -------
Euh.. No. Sorry.
(suns statements in javadoc about thread are known to be very forgiving for JVM
implementors. Most if not all serious jvm have correct priorities.)

There are plenty of JVMs out there that do correctly implements priority.
And thrust me, it works. Here are some examples.
Please verify by yourself.

-screen updater toggles back and forth between prio 4 and 6. It help propmptness
of drawing.

-finalizer has low prio, for obvious reason. It does run seldomly, as expected
in idle times.

-SEDA architecture like sandstorm works great!
I myself created a seda thread manager based on priority and load detection. It
runs very nicely on sun, ibm, jrockit JVM, on both win32 and linux platform.

Besides, I raise the tomcat connector threads in a dirty way: enumerate thread,
match name with regex, and raise prio to 7 (because I use prio 1 to 6 for
sandstorm).

Trust me, it really balances stage & queue load and work well. And with that
tomcat prio raised, my web UI is responsive and I keep the control.

In other systems, with jmx timer and with container sheduling
JSR 236 titled "Timer for Application Servers"
http://jcp.org/en/jsr/detail?id=236
thread priority will become a serious concern.

Please consider this RFE with "normal priority" (hehehe!)

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message