On Thu, Apr 18, 2002 at 12:08:24AM -0700, Brian Pane wrote: > httpd listening on one port: > Requests/ Mean request CPU CPU > MPM second time (ms) load utilization > ----------------------------------------------------------- > Threadpool 854 55.5 4.8 52% > Leader/follower 957 39.5 6.8 72% > Worker 892 31.4 7.0 70% > > > httpd listening on two ports: > Requests/ Mean request CPU CPU > MPM second time (ms) load utilization > ----------------------------------------------------------- > Threadpool 848 54.5 4.8 53% > Leader/follower 814 58.4 4.5 51% > Worker 881 47.7 5.1 59%
(Assuming you ran with AcceptMutex pthread...) Do you still have no idea why Leader/follower is getting nailed when there are two listeners (while worker has a dropoff, it isn't quite that severe)? So, threadpool is slower on single listeners but has almost no noticable difference when having two listeners versus one. Is this because threadpool doesn't use S_L_U_A? With one listener, how does worker have a better mean but a noticably worse rps count? Were there some requests that skewed the mean? Also, while I'm not terribly sure how valuable this might be to you, I think it might be good to see how prefork compares on this same test. After all, it is our default MPM and will be until we can prove to people (esp. committers) how much better threading can be. -- justin
