> Ok, now we're on the same page. I see this as a problem as well, but I > don't think this is what is causing the problem described earlier in this > thread. Considering how unlikely it is that all of the threads on one > process are on long-lived connections, I don't see this as a critical > short-term problem. What is more likely is that 'ab', used to observe > this phenomon, is flawed in a way that prevents it from truly testing the > concurrent processing capabilities of the worker MPM, when it is possible > for a request on a different socket to be returned sooner than another. > Flood would be much more appropriate for this kind of a test.
So, what you are saying is that it isn't common for Apache httpd to be used for sites that serve large images to people behind modems. Right? And therefore we shouldn't fix the only MPM that exists solely because sites that mostly serve large images to people behind modems didn't want the memory overhead of prefork. Think about it. ....Roy
