apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 42889] - Thread pooling declaration fix and enhancements
Date Thu, 26 Jul 2007 12:01:35 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=42889>.
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=42889





------- Additional Comments From Joe.Mudd@sas.com  2007-07-26 05:01 -------
Yes, the implementation makes sense and I can go either way as well.

My comment was more of from a thread in hand position.  I was thinking that if 
the thread didn't really timeout, then there must be enough work to keep it 
busy and it should be given another chance to waste away.

As an aside, I updated the thread pool code to change the state from probation 
to run after a task had been processed.  In my use of the thread pool (~50 
second run on dual core Wintel), giving an idle thread that woke up and did 
work another chance changed the number of reaped idle threads from 28 to 17 and 
shaved around 4 seconds off of the run.

Thanks again for the implementation and your very prompt attention.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org


Mime
View raw message