On 3/21/11 9:51 AM, Luca Morandini wrote: > On 03/21/2011 09:16 AM, Arne Kepp wrote: >> Not sure about the intermittent slowdowns, > That could suggest some swapping taking place (hence slowing it down) until > the > memory load relents and no swapping is needed any more... unless it drops > requests, freeing up resources. > Possible. With mod_prefork it is also easy to run out of processes, the default configuration only serves 150 simultaneous requests or so. That's only 30 to 40 browsers before it refuses to take more connections.
>> At that point the additional TCP/IP connections + threads in Apache are >> not neglible anymore. > Indeed: I stand corrected. > > By the way, when the load is expected to be heavy, I would push GWC to the > edge of > the network, de-copupling it from GeoServer and putting it on the front-end > (HTTPd) server, where any static content should be. Yeah, agree about the decoupling and putting it as far up front as possible. Both Tomcat and Jetty are pretty good and easily saturate gigabit even with a mixed clientele. -Arne ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
