Proxmox/pve-manager
5
0
Fork 0
Code Pull Requests Releases Activity

pvestatd: run at lease 10 cycles

Browse Source 
Comment from Stefan: I've seen that it takes up to 10 cycles to have a
constant memory size. I think this is due to the fact that perls garbage
collection is not running every after each cycle.
This commit is contained in:
Dietmar Maurer 2012-10-29 13:08:46 +01:00
parent 6d00167c16
commit c1614c8c0e
3 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bin/pvestatd
View File

@ -384,7 +384,7 @@ for (;;) { # forever
my $mem = PVE::ProcFSTools::read_memory_usage();
if (!defined($initial_memory_usage)) {
if (!defined($initial_memory_usage) || ($cycle < 10)) {
$initial_memory_usage = $mem->{resident};
} else {
my $diff = $mem->{resident} - $initial_memory_usage;

6
debian/changelog.Debian vendored
View File

@ -1,3 +1,9 @@
pve-manager (2.2-26) unstable; urgency=low
* pvestatd: fix server reload (run at least 10 cycles)
-- Proxmox Support Team <support@proxmox.com> Mon, 29 Oct 2012 13:08:20 +0100
pve-manager (2.2-25) unstable; urgency=low
* pvestatd: fix server reload (due to memory leak)

2
defines.mk
View File

@ -2,7 +2,7 @@ RELEASE=2.2
VERSION=2.2
PACKAGE=pve-manager
PACKAGERELEASE=25
PACKAGERELEASE=26
BINDIR=${DESTDIR}/usr/bin
PERLLIBDIR=${DESTDIR}/usr/share/perl5