On Tue, Aug 3, 2010 at 8:05 AM, Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote: >> here's the server stats: >> http://server-stats.haiku-os.org/stats?host=vmdev.haiku-os.org&plugin=apache&plugin=cpu&plugin=df&plugin=disk&plugin=interface&plugin=load&plugin=memory&plugin=postgresql&plugin=processes&plugin=vmem×pan=hour&button=Ok >> >> >> ...Not sure what caused the memory & processes to spike. >> baron:/etc/init.d # service VM-dev restart >> >> >> After restarting ( baron:/etc/init.d # service VM-dev restart ), it's >> memory usage went past 1536, causing it to be non-responsive. >> I increased the ram to 2048 in /etc/init.d/VM-dev and after another >> restart, it seems to be happy. >> 1390 root 20 0 2190m 405m 1380 S 1 5.1 0:48.23 qemu-kvm > > Thanks for the info. I have checked the logs, but did not find anything that > would explain the increased memory use, especially not directly after boot. > :-\ > > Just now, I have reconfigured (and restarted) all VMs to let their I/O bypass > the hosts cache, which should considerably lower the memory pressure on > baron. Before, the image-file as well as the VMs disk blocks had to travel > through the host cache. Now it should be only the image-file. Looking at the stats now, I don't really see that vmdev needed more memory than it had - I suspect that whatever caused it to fail that day would still cause it to fail with 2gb RAM as it must have gone off the deep end at that time. http://baron.haiku-os.org/stats?host=baron.haiku-os.org&host=vmdev.haiku-os.org&host=vmsvn.haiku-os.org&host=vmweb.haiku-os.org&plugin=memory×pan=month&button=Ok Baron could benefit from having a little extra cache room, however... perhaps we should reduce vmdev's memory back down to 1.5gb? - Urias