On Tuesday, March 13, 2012 10:11:17 AM, Tom Evans wrote: > > On Tue, Mar 13, 2012 at 4:58 PM, William Taylor > <willi...@corp.sonic.net> wrote: >> >> On Tuesday, March 13, 2012 2:42:35 AM, Tom Evans wrote: >>> >>> >>> On Mon, Mar 12, 2012 at 7:39 PM, William Taylor >>> <willi...@corp.sonic.net> wrote: >>>> >>>> >>>> Previously posted to dev and bugs. Posting here also in hopes of >>>> capturing a greater audience that might have come >>>> across this issue before. >>>> >>>> We have written a modules for apache that for certain reasons requires >>>> one hit per child. >>>> On apache 1.3 this worked fine with a minor tweak to >>>> SCOREBOARD_MAINTENANCE_INTERVAL >>>> setting it to 10000 from 1000000. >>>> >>>> Note that this behavior can be tested without our module by setting >>>> "MaxRequestsPerChild 1" >>>> >>> >>> >>> >>> This will get you pathologically bad performance. You may have very >>> important reasons for doing this, but it goes completely against how >>> Apache wants to work. >>> >>> Nevertheless, if you can identify the regression, that would also be >>> good! >>> >> >> >> I'm not questioning the decrease in performance. I'm well aware of that >> fact. :) >> But I think apache 2.2.x should be able to perform as well as apache >> 1.3.x in the >> same scenario. >> > > > Indeed. But for the project, running in a silly way and saying "it's > slow" isn't going to make this a particularly high priority for > someone *who isn't you* to investigate. The old joke:
I wouldn't say it's silly, but definitely not the norm and obviously a low priority for everyone else. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
