Greg Ames wrote: > > > That said, I guess the threaded mpm really isn't ready for prime time, > > unless: > > * you are prepared to tune it (we can help), or > > * you know that your download times are all pretty uniform. > > > > I should probably elaborate some on the tuning, in case folks want to > play. Basic stuff first, more advanced stuff after more sleep: > D'oh! forgot to mention the simplest way to bypass this problem: set MaxRequestsPerChild to 0. If you can get by with that, you're done, ignore the rest. > The threaded MPM currently uses MaxRequestsPerChild just like Apache 1.3 > and 2.0 prefork do, tha it, when a process hits the magic number, it > quits accepting new connections. But since ThreadsPerChild will usually > be > 1 , one thread can be serving something that takes a really long > time, [much stuff deleted here] Greg
- Re: thread locking within apr file io Greg Ames
- Re: thread locking within apr file io Paul J. Reder
- Re: thread locking within apr file io Justin Erenkrantz
- Re: thread locking within apr file i... Justin Erenkrantz
- Re: thread locking within apr f... rbb
- Re: thread locking within apr f... Victor J. Orlikowski
- Re: thread locking within apr f... David Reid
- Re: thread locking within apr file io Greg Ames
- Re: thread locking within apr file i... Paul J. Reder
- Re: thread locking within apr file i... Greg Ames
- Re: thread locking within apr f... Greg Ames
- Re: thread locking within apr file io Paul J. Reder
- Re: thread locking within apr file i... Bill Stoddard
- Re: thread locking within apr f... Paul J. Reder
- Re: thread locking within apr file io Greg Stein
- Re: thread locking within apr file io Chuck Murcko
- RE: thread locking within apr file io Ian Holsman
