Re: [Resin-interest] How do I limit the number concurrent requests from mod_caucho in Apache to Resin?
On 04/16/2013 06:11 PM, Scott Ferguson wrote: > On 4/16/13 8:24 AM, Vidar Skaugen wrote: >> Hi. We have a web app that uses quite a bit of memory, so after roughly >> 20 instances per GB allocated memory it starts to spend more and more >> time doing garbage collection. With enough concurrent connections it >> grinds to a halt. >> >> I've been trying to limit the number of threads that are started at >> once. seems to work for this, and does what I want >> when I setup Resin as a http server. However I've been unable to get it >> to work with mod_caucho. Setting in or >> setting port_thread_max in resin.properties does not seem to affect the >> traffic coming in from mod_caucho. > > If this is for Resin 4.0, you might try , which has the > same syntax as and lets you configure the 6800 port properties. > The config looks like: > > > > > 20 > >... > > If you're in a clustered environment, that limit might cause problems > with the clustering. Thank you very much for the reply Scott. I wasn't aware that was an option. After extrapolating from your reply I ended up using: 20 Also, sorry for the late reply. I've been testing it quite a bit since there's still a problem somewhere with an occasional response getting dropped, but I'm pretty sure now that the port-thread-max bit works perfectly and it's an unrelated issue (there are quite a few places if could happen since it goes through apache and mod_caucho before reaching resin). Regards - Vidar Engh Skaugen ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] How do I limit the number concurrent requests from mod_caucho in Apache to Resin?
On 4/16/13 8:24 AM, Vidar Skaugen wrote: > Hi. We have a web app that uses quite a bit of memory, so after roughly > 20 instances per GB allocated memory it starts to spend more and more > time doing garbage collection. With enough concurrent connections it > grinds to a halt. > > I've been trying to limit the number of threads that are started at > once. seems to work for this, and does what I want > when I setup Resin as a http server. However I've been unable to get it > to work with mod_caucho. Setting in or > setting port_thread_max in resin.properties does not seem to affect the > traffic coming in from mod_caucho. If this is for Resin 4.0, you might try , which has the same syntax as and lets you configure the 6800 port properties. The config looks like: 20 ... If you're in a clustered environment, that limit might cause problems with the clustering. -- Scott > > The only way I've been able to limit it at all is to set thread-max in > really low (20-ish seems to be the minimum that has a chance of > working). Of course I don't want to do this, since this limits all > system threads and setting it too low causes weird problems if resin > runs out of threads. > > Setting keepalive-max, connection-max, or thread-idle-max in server > doesn't help, and accept-thread-max isn't applicable. Is there a setting > I'm overlooking somewhere? > >Regards >- Vidar Engh Skaugen > > > ___ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] How do I limit the number concurrent requests from mod_caucho in Apache to Resin?
Hi. We have a web app that uses quite a bit of memory, so after roughly 20 instances per GB allocated memory it starts to spend more and more time doing garbage collection. With enough concurrent connections it grinds to a halt. I've been trying to limit the number of threads that are started at once. seems to work for this, and does what I want when I setup Resin as a http server. However I've been unable to get it to work with mod_caucho. Setting in or setting port_thread_max in resin.properties does not seem to affect the traffic coming in from mod_caucho. The only way I've been able to limit it at all is to set thread-max in really low (20-ish seems to be the minimum that has a chance of working). Of course I don't want to do this, since this limits all system threads and setting it too low causes weird problems if resin runs out of threads. Setting keepalive-max, connection-max, or thread-idle-max in server doesn't help, and accept-thread-max isn't applicable. Is there a setting I'm overlooking somewhere? Regards - Vidar Engh Skaugen ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
