Bug#491226: boincmgr: does not respect VM occupation limits
Hi Frank, I just made some tests On Tue, Aug 26, 2008 at 16:36, Frank S. Thomas [EMAIL PROTECTED] wrote: So if I'm right, the client should never leave applications in memory which is opposed to the other bug you reported. *sigh* :-) well, it shows of they are related (see below) Frankly, I don't know. But it would be interesting if you could modify those values to find out if it affects RAM usage. For example, set them to 25.0 and 50.0, restart the client and monitor the client's RAM usage. To monitor BOINC's RAM usage the attached script may be helpful: $ watch -n 0.5 ./boinc-mem-usage.sh In theory, BOINC's total resident set size (in %) should never exceed ram_max_used_idle_pct. Before the tests I got: $ egrep ram_max_used_idle_pct|ram_max_used_busy_pct /etc/boinc-client/global_prefs_override.xml ram_max_used_busy_pct50.00/ram_max_used_busy_pct ram_max_used_idle_pct90.00/ram_max_used_idle_pct $ ~/tmp/boinc-mem-usage.sh Host's total memory: 4058168 KiB 3963.05 MiB Host's total swap: 0 KiB 0.00 MiB BOINC's total resident set size:1231356 KiB 1202.50 MiB BOINC's total virtual memory size: 1331948 KiB 1300.73 MiB BOINC's total resident set size: 30.3% BOINC's total virtual memory size: 32.8% Then I set: $ egrep ram_max_used_idle_pct|ram_max_used_busy_pct /etc/boinc-client/global_prefs_override.xml ram_max_used_busy_pct25.00/ram_max_used_busy_pct ram_max_used_idle_pct50.00/ram_max_used_idle_pct guess what? $ ~/tmp/boinc-mem-usage.sh Host's total memory: 4058168 KiB 3963.05 MiB Host's total swap: 0 KiB 0.00 MiB BOINC's total resident set size:1629944 KiB 1591.74 MiB BOINC's total virtual memory size: 1782020 KiB 1740.25 MiB BOINC's total resident set size: 40.2% BOINC's total virtual memory size: 43.9% The problem is that the process put on hold due to Waiting for memory are indeed *left in memory* so my machine went trashing (I got to kill boinc from a laptop). If you need some other tests, simply ask (I'd like to see boinc bug free :) ). Cheers, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491226: boincmgr: does not respect VM occupation limits
Hi Sandro, On Monday 25 August 2008 22:40, Sandro Tosi wrote: On Mon, Aug 25, 2008 at 19:53, Frank S. Thomas [EMAIL PROTECTED] wrote: I'm not totally sure but I think vm_max_used_pct is only used to determine if enough swap space is available to leave suspended applications in memory if leave_apps_in_memory is set. So for example if vm_max_used_pct is set to 25.0 and you have 1 GB of swap space, BOINC would only use 250 MB of it for suspended applications. Well, on this machine there is no swap space ;) So if I'm right, the client should never leave applications in memory which is opposed to the other bug you reported. *sigh* :-) If you want to limit RAM usage, you should adjust ram_max_used_busy_pct and ram_max_used_idle_pct in global_prefs_override.xml. These are the values for the keys: $ egrep ram_max_used_idle_pct|ram_max_used_busy_pct /etc/boinc-client/global_prefs_override.xml ram_max_used_busy_pct50.00/ram_max_used_busy_pct ram_max_used_idle_pct90.00/ram_max_used_idle_pct It seems a safe situation, but the problem appears anyhow (and I didn't change those parameters in the meantime). I was on 6.2.12 while now I'm on 6.2.14 (waiting for .18 to be built for amd64) so I don't know if in the meantime it was fixed or not. Frankly, I don't know. But it would be interesting if you could modify those values to find out if it affects RAM usage. For example, set them to 25.0 and 50.0, restart the client and monitor the client's RAM usage. To monitor BOINC's RAM usage the attached script may be helpful: $ watch -n 0.5 ./boinc-mem-usage.sh In theory, BOINC's total resident set size (in %) should never exceed ram_max_used_idle_pct. Cheers, -- Frank S. Thomas [EMAIL PROTECTED] PGP public key ID: 0xDC426429 Debian Developerfinger fst/[EMAIL PROTECTED] boinc-mem-usage.sh Description: application/shellscript signature.asc Description: This is a digitally signed message part.
Bug#491226: boincmgr: does not respect VM occupation limits
reassign 491226 boinc-client 6.2.12-1 thanks Hi Sandro, On Thursday 17 July 2008 20:58, Sandro Tosi wrote: I've set limits for VM usage: zion:/debs# grep vm_max_used_pct etc/boinc-client/global_prefs_override.xml vm_max_used_pct75.00/vm_max_used_pct I'm not totally sure but I think vm_max_used_pct is only used to determine if enough swap space is available to leave suspended applications in memory if leave_apps_in_memory is set. So for example if vm_max_used_pct is set to 25.0 and you have 1 GB of swap space, BOINC would only use 250 MB of it for suspended applications. but boicmgr didn't respect them, and I got 4 garli processes (each one takes 1Gb of ram) on my 4Gb Ram machine, and the box got freezed. If you want to limit RAM usage, you should adjust ram_max_used_busy_pct and ram_max_used_idle_pct in global_prefs_override.xml. Cheers, -- Frank S. Thomas [EMAIL PROTECTED] PGP public key ID: 0xDC426429 Debian Developerfinger fst/[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Bug#491226: boincmgr: does not respect VM occupation limits
Hi Frank, On Mon, Aug 25, 2008 at 19:53, Frank S. Thomas [EMAIL PROTECTED] wrote: On Thursday 17 July 2008 20:58, Sandro Tosi wrote: I've set limits for VM usage: zion:/debs# grep vm_max_used_pct etc/boinc-client/global_prefs_override.xml vm_max_used_pct75.00/vm_max_used_pct I'm not totally sure but I think vm_max_used_pct is only used to determine if enough swap space is available to leave suspended applications in memory if leave_apps_in_memory is set. So for example if vm_max_used_pct is set to 25.0 and you have 1 GB of swap space, BOINC would only use 250 MB of it for suspended applications. Well, on this machine there is no swap space ;) but boicmgr didn't respect them, and I got 4 garli processes (each one takes 1Gb of ram) on my 4Gb Ram machine, and the box got freezed. If you want to limit RAM usage, you should adjust ram_max_used_busy_pct and ram_max_used_idle_pct in global_prefs_override.xml. These are the values for the keys: $ egrep ram_max_used_idle_pct|ram_max_used_busy_pct /etc/boinc-client/global_prefs_override.xml ram_max_used_busy_pct50.00/ram_max_used_busy_pct ram_max_used_idle_pct90.00/ram_max_used_idle_pct It seems a safe situation, but the problem appears anyhow (and I didn't change those parameters in the meantime). I was on 6.2.12 while now I'm on 6.2.14 (waiting for .18 to be built for amd64) so I don't know if in the meantime it was fixed or not. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491226: boincmgr: does not respect VM occupation limits
Package: boinc-manager Version: 6.2.12-1 Severity: important File: /usr/bin/boincmgr Hello, I've set limits for VM usage: zion:/debs# grep vm_max_used_pct etc/boinc-client/global_prefs_override.xml vm_max_used_pct75.00/vm_max_used_pct but boicmgr didn't respect them, and I got 4 garli processes (each one takes 1Gb of ram) on my 4Gb Ram machine, and the box got freezed. Please give it a look, since it has the potential to completely block a workstation (reboot would be needed then). Thanks, Sandro -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages boinc-manager depends on: ii libc62.7-12 GNU C Library: Shared libraries ii libstdc++6 4.3.1-6 The GNU Standard C++ Library v3 ii libwxbase2.6-0 2.6.3.2.2-2 wxBase library (runtime) - non-GUI ii libwxgtk2.6-02.6.3.2.2-2 wxWidgets Cross-platform C++ GUI t Versions of packages boinc-manager recommends: ii boinc-client 6.2.12-1 core client for the BOINC distribu boinc-manager suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
