Re: getting the thread pool to shrink
Quartz <[email protected]> Fri, 1 Aug 2003 15:32:28 -0700 (PDT)
| Newsgroups | gmane.comp.java.seda.user |
|---|---|
| Message-ID | <[email protected]> |
(I answer my own questions for the benefit of others and for archives) Sorry, nothing wrong, it does work, only it take a somewhat steady state for the thread pool threads to expire and leave the threadpool. Got my steady 24 threads after leaving it alone for 15 minutes. But can't say exactly how long it took... --- Quartz <[email protected]> wrote: > Hi, > > Context: > > -the queue of a slow stage is posted at every 100 ms. (the basic test, timer at 100ms, Generic > sleeps at 2400 ms, batchController not enabled but batchController.maxBatch at 10) > > -the stage catches up his back log when growing above 40 threads. > > -in theory, the stage could run only with 24 threads (task is a sleep of 2400 ms) > > -the idleThreshold has been made smaller than blockTime so that on the first timeout, the thread > is removed from the pool > > -sizeController delay is at 100ms for quick resizing > > > Problem: > > I guessed that if the blockTime is small enough near the expected 100ms of the inputs, threads > would expire quickly instead of stealing the item typically taken by the 24th oldest processing > thread coming back. > > But that doesn't work. What is wrong with the config? __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01