mirror of
https://git.proxmox.com/git/pve-manager
synced 2025-05-29 13:51:35 +00:00
pvestatd: run at lease 10 cycles
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:
parent
350b3b46e9
commit
9dbdda49d0
@ -384,7 +384,7 @@ for (;;) { # forever
|
|||||||
|
|
||||||
my $mem = PVE::ProcFSTools::read_memory_usage();
|
my $mem = PVE::ProcFSTools::read_memory_usage();
|
||||||
|
|
||||||
if (!defined($initial_memory_usage)) {
|
if (!defined($initial_memory_usage) || ($cycle < 10)) {
|
||||||
$initial_memory_usage = $mem->{resident};
|
$initial_memory_usage = $mem->{resident};
|
||||||
} else {
|
} else {
|
||||||
my $diff = $mem->{resident} - $initial_memory_usage;
|
my $diff = $mem->{resident} - $initial_memory_usage;
|
||||||
|
6
debian/changelog.Debian
vendored
6
debian/changelog.Debian
vendored
@ -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
|
pve-manager (2.2-25) unstable; urgency=low
|
||||||
|
|
||||||
* pvestatd: fix server reload (due to memory leak)
|
* pvestatd: fix server reload (due to memory leak)
|
||||||
|
@ -2,7 +2,7 @@ RELEASE=2.2
|
|||||||
|
|
||||||
VERSION=2.2
|
VERSION=2.2
|
||||||
PACKAGE=pve-manager
|
PACKAGE=pve-manager
|
||||||
PACKAGERELEASE=25
|
PACKAGERELEASE=26
|
||||||
|
|
||||||
BINDIR=${DESTDIR}/usr/bin
|
BINDIR=${DESTDIR}/usr/bin
|
||||||
PERLLIBDIR=${DESTDIR}/usr/share/perl5
|
PERLLIBDIR=${DESTDIR}/usr/share/perl5
|
||||||
|
Loading…
Reference in New Issue
Block a user