Instead, we should measure usage at startup (or first iteration), then allow to grow a few MBs?
> -----Original Message----- > From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel- > boun...@pve.proxmox.com] On Behalf Of Stefan Priebe - Profihost AG > Sent: Freitag, 26. Oktober 2012 13:23 > To: pve-devel@pve.proxmox.com > Subject: [pve-devel] pvestatd memory detection is too low > > Hello, > > my memory consumption of pvestatd seems to be constant now but it is at > 47MB. So the limit with 35MB seems to be too small. > > I would suggest the following fix. > > Stefan > > commit 047101ff8d05432b8bd67aba8074bd110a94d5a2 > Author: Stefan Priebe <s.pri...@profihost.ag> > Date: Fri Oct 26 13:08:49 2012 +0200 > > bump memory usage info to 100MB for pvestatd > > diff --git a/bin/pvestatd b/bin/pvestatd index 5513c85..c3a609a 100755 > --- a/bin/pvestatd > +++ b/bin/pvestatd > @@ -382,7 +382,7 @@ for (;;) { # forever > > my $mem = PVE::ProcFSTools::read_memory_usage(); > > - if ($mem->{resident} > (35*1024*1024)) { > + if ($mem->{resident} > (100*1024*1024)) { > syslog ('info', "restarting server after $cycle cycles to ". > "reduce memory usage (free $mem->{resident} bytes)"); > restart_server (); > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
