Stas Bekman wrote: >Steve Hay wrote: > > >>I have to >>increase ThreadsPerChild in the mpm_winnt.c section >>(Apache-Test/lib/Apache/TestConfig.pm) to some value higher than 20. >>I'm not sure how much higher it needs to be, but 50 works for me. >> >> > >the worker mpm works just fine with just 2 threads, just like his prefork cousin: > ><IfModule worker.c> > StartServers 1 > MaxClients 2 > MinSpareThreads 2 > MaxSpareThreads 2 > ThreadsPerChild 2 > MaxRequestsPerChild 0 ></IfModule> > >that means that those extra threads on win32 are used for something else. >Could you figure out why they are needed and what keeps them busy? Try using >the new Apache::VMonitor. It will show you all the active threads and what >they are doing or done recently. > I've looked at that before and can't use it because it depends on GTop which requires libgtop which we haven't got in Windoze land.
> >Nothing special that I can think of has changed since _12, besides having a >bigger test suite. For example this could add to the startup time. A-T pings >the server waiting till it's ready. Perhaps these pings (GET /index.html >HTTP1.1) when the server is not ready, consume threads, get them blocking and >at some point there are no more threads to ping with. If that's the case, it >sounds like a bad bug in Apache to me. > >You could test with ModPerl-Registry's make test - it should start much faster >and you probably won't have any problems with 20 threads. Now add sleep 60 or >so in modperl_extra.pl and see if you run out of threads. > ModPerl-Registry's "nmake test" runs fine with 20 threads (waited 31 sec to start up). I added sleep 60 into modperl_extra_startup.pl and it still runs fine with only 20 threads (waited 151 sec to start up this time). So I don't think it's a problem with ping. I'll try chopping some of the new (post _12) tests out to see if I can get it working again. - Steve ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email. -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
