On Tue, Oct 14, 2003 at 11:26:45AM -0400, Edward J. Huff wrote: > Nobody is on #FreeNet. I'm looking at this now. > > *** Does this mean you're really back? > Anybody here? > If not, I think I know how to fix QThreadFactory so that it > transparently queues any excess jobs and lets the next thread > which comes back (or the next thread created by thread creation > thread) take it. Have to look at the code but it should > work. Since we have hundreds of threads, one of them is > going to finish soon... Thread creation thread will be the > only one to do new thread. It will run every say 100ms and > make more if needed. > > -- Ed Huff
Well... maybe as a last resort. But arbitrarily queueing jobs will definitely cause us to timeout etc. In the long term, all jobs will be nonblocking with the exception of those doing disk I/O - and therefore, they will all be run either immediately or on the single fast-jobs thread. It might be useful in order to allow an absolute maximum number of threads at the expense of performance. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
