Hi, On 15 October 2010 21:10, Alexander von Gluck IV <kallisti5@xxxxxxxxxxx> wrote: > > On Fri, 15 Oct 2010 20:57:30 +0200, Oliver Tappe > <zooey@xxxxxxxxxxxxxxx> wrote: >> Hi Urias, >> >> On 2010-10-15 at 20:18:11 [+0200], Urias McCullough >> <umccullough@xxxxxxxxx> wrote: >>> On Fri, Oct 15, 2010 at 11:11 AM, Urias McCullough >>> <umccullough@xxxxxxxxx> wrote: >>> >> http://baron.haiku-os.org/stats?host=vmweb.haiku-os.org&plugin=memory×pan=day&button=Ok >>> > >>> > Ok, I'll try to fix this - I should have access to kill it, and it >>> > should be documented where I think it is :) >>> >>> I have bumped the memory on "vmweb" to 2557mb and restarted it (was >>> killed hard): >> >> That's fine - once the server is under heavy pressure, it won't serve >> >>> Hopefully it will stay up :P >> >> so far, it seems to stay in bounds. >> >> But, judging from the little info I have right now, the apache >> processes eat a lot of memory. If >> at all possible, we should try to move to a threaded apache setup, >> but I'm not sure that's >> feasible with Drupal being a php application. Anyway, I suppose we >> should really invest some >> more time to optimize our Drupal setup. Ideally, we'd pre-render >> unchanged pages and serve them >> statically, at least Drupal seems to support that in principle. >> >> cheers, >> Oliver > > Personally I prefer Cherokee over Apache.. it does a lot more with > less and uses FastCGI: > > http://www.cherokee-project.com/ > > > As an alternative we could switch to fastcgi php on Apache. > FastCGI handles heavy load better but might consume a little more > memory as it requires > resident php server processes that could be placed on local/remote > nodes and connected > to by Apache to serve php script requests. Thanks for the suggestion, but we should separate performance issues from this issue, which seems more like a major bug that occurs during high loads than the result from this high load. N>