Re: mod_fcgid concurrency bottleneck, issue#53693

2012-08-16 Thread William A. Rowe Jr.
On 8/15/2012 8:23 PM, pqf wrote: > But since someone said remove this sleep(), the server work fine without > bottleneck(Maybe > he didn't notise the warm up issue?), so I thought remove the sleep() is a > good idea. But > reduce the time of sleep() is fine to me too. > Any other idea? Can we in

Re: Re: mod_fcgid concurrency bottleneck, issue#53693

2012-08-16 Thread pqf
procmgr_post_spawn_cmd(maybe it should be renamed to procmgr_send_spawn_cmd) will keep blocking while PM is creating a new process, after procmgr_post_spawn_cmd() return, there should be a process ready there waiting for accept. 2012-08-16 pqf 发件人:William A. Rowe Jr. 发送时间:2012-08-16 15:23

Re: Re: mod_fcgid concurrency bottleneck, issue#53693

2012-08-16 Thread Lazy
2012/8/16 pqf : > Hi, Michal > My solution do "add availability to each class", which is the > procmgr_post_spawn_cmd() call in each loop do. > The sleep() call is intrudused for a stress test without warm up time, in > this case, mod_fcgid will create more processes than a slow start one(each > pr

回复: Re: Re: mod_fcgid concurrency bottleneck, issue#53693

2012-08-16 Thread pqf
How about this: 1. procmgr_post_spawn_cmd() now return a status code from PM, so process handler now know the spawn request is denyed or not. 2. if a new process is created, no sleep is needed. 3. if no process is created, sleep a while 2012-08-16 pqf 发件人:Lazy 发送时间:2012-08-16 16:47 主题:Re: R

Re: Proposed T&R for this Friday

2012-08-16 Thread Jim Jagielski
The -deps tarball was hidden (one had to look around for it) so I just added a note that sometimes we provide it as a convenience. On Aug 15, 2012, at 4:52 AM, Rainer Jung wrote: > On 14.08.2012 23:17, Jim Jagielski wrote: >> With my Mom's hospitalization and stuff, this kinda slipped... > > I h

Re: Linking mod_ssl with a specific OpenSSL version

2012-08-16 Thread Kaspar Brand
On 12.8.12 20:01, Ben Laurie wrote: > On Sun, Aug 12, 2012 at 5:23 PM, Kaspar Brand wrote: >> a workaround is to call configure with >> suitable {CPP,LD}FLAGS, i.e. >> >> CPPFLAGS=-I${openssl_build_dir}/include \ >> LDFLAGS=-L${openssl_build_dir} \ >> ./configure ... >> >> (when using the sh