Notebook w/ 4GB RAM - "waiting for memory"


Advanced search

Message boards : Number crunching : Notebook w/ 4GB RAM - "waiting for memory"

Author Message
Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5910 - Posted: 1 Jan 2017, 18:49:55 UTC

Besides having ATLAS running on two desktop PCs, I now tried to attach it to one of my notebooks. CPU virtualisation no problem; however, there are only 4 GB RAM which cannot be extended.
First, I tried a 1x1 multicore task, and a few seconds after starting, BOING showed "waiting for memory" in the "status" column. Then I remembered that there is a setting server-side which requests around 8.9GB RAM for each multicore task.
So I switched to single-core tasks - however, same problem. Although roughly 2.5GB of the total 4 GB RAM are free, it says again "waiting for memory".
Why so?

I remember that I have read somewhere in the forum that people are crunching ATLAS with 4GB RAM.
Any hints as to what I could do?

Profile HerveUAE
Avatar
Send message
Joined: 18 Dec 16
Posts: 44
Credit: 509,829
RAC: 0
    
Message 5912 - Posted: 2 Jan 2017, 9:22:29 UTC - in response to Message 5910.

Have you tried configuring ATLAS_MCORE in app_congif.xml with 3300 Mbytes and the Conputing preferences in BOINC Manager to allow using 100% of both CPU and RAM?

If it works like this, trying bringing down those 100% to the minimum that allows the task to work.

Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5914 - Posted: 2 Jan 2017, 9:43:32 UTC

Herve, did this indeed work on your system with 4 GB RAM?

Because, in view of what I was reading here in the forum:

ATLAS_MCORE requests a work package size of 8.9 GB for each WU.
This value is set in the server reply by the variable <rsc_memory_bound> and can not be changed on the client-side


I would imagine that a multicore task will never work on a 4GB RAM system.

Profile Yeti
Avatar
Send message
Joined: 20 Jul 14
Posts: 699
Credit: 22,597,832
RAC: 0
    
Message 5915 - Posted: 2 Jan 2017, 10:38:53 UTC


  1. Crunch only SingleCoreTasks
  2. optimize you memory-settings from this hardcopy:




Maybe you should allow to use 100% of the memory to get it working on a 4 GB machine

Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5916 - Posted: 2 Jan 2017, 11:31:06 UTC

Checking the BOINC settings, I realized that RAM usage was set to 65%. So I increased it to 100%.
CPU usage and time were/are at 100%.

Single cores now start, so the problem was indeed the wrong RAM setting before.

However, it turns out that regardless of how long a WU is running since it startet - CPU usage always is only 4 seconds.
Either the current single core WUs happen to be defective (what we had once and so often in the past), or for some unknown reason, they cannot be crunched properly on my notebook.

Profile Yeti
Avatar
Send message
Joined: 20 Jul 14
Posts: 699
Credit: 22,597,832
RAC: 0
    
Message 5917 - Posted: 2 Jan 2017, 11:36:12 UTC - in response to Message 5916.

CPU usage always is only 4 seconds.

Once again, work through my checklist

Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5918 - Posted: 2 Jan 2017, 15:50:58 UTC

It came into my mind that I saw the same situation (after start of the task, CPU only works for a few seconds) some time ago with a PC having an older CPU which was not capable of virtualization (a fact which I had not checked beforehand).

So, in this case here, I looked up the BIOS and found out that the virtualization was switched off. And that was exactly it. ATLAS crunching now works :-)

maeax
Send message
Joined: 25 Jun 14
Posts: 50
Credit: 1,700,662
RAC: 0
    
Message 5941 - Posted: 7 Jan 2017, 20:51:03 UTC - in response to Message 5914.
Last modified: 7 Jan 2017, 20:52:50 UTC

I would imagine that a multicore task will never work on a 4GB RAM system.


Have made a test with Windows HomeServer 2011 and 4 GByte RAM.
TWO multicore-Tasks (ONE CPU) where finished successful.

3 GByte as maximum for GigaByte Disk Space in Boinc.

This is only a test to see Multicore-Tasks are running with 4 GByte RAM.

http://atlasathome.cern.ch/results.php?hostid=67596

Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5947 - Posted: 8 Jan 2017, 14:10:31 UTC - in response to Message 5941.
Last modified: 8 Jan 2017, 14:19:33 UTC

3 GByte as maximum for GigaByte Disk Space in Boinc.

why so? The vm_image.vdi for each task is about 2 GB.
So if you limit the Disk Space to 3 GB, there would not be enough disk space for 2 tasks.

Further question: did you use an app_config.xml to manage 2 multicore WUs running simultaneously?
Or did you do it by some kind of other settings?

maeax
Send message
Joined: 25 Jun 14
Posts: 50
Credit: 1,700,662
RAC: 0
    
Message 5952 - Posted: 8 Jan 2017, 15:00:02 UTC
Last modified: 8 Jan 2017, 15:02:24 UTC

The limit of 3 GByte is inclusive RAM-use. The OS is using 1 GByte itself.
If there is no limit of 3 GByte, then the Server crashed.

It was only a Test to see if it is working with one task and one CPU as multicore.

Have no app_config.xml.

Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5953 - Posted: 8 Jan 2017, 15:13:48 UTC - in response to Message 5952.

It was only a Test to see if it is working with one task and one CPU as multicore.

thanks for your quick reply.
However, I am somewhat confused now, since in an earlier posting you were talking about 2 multicore tasks (1 core ea.).

Profile Yeti
Avatar
Send message
Joined: 20 Jul 14
Posts: 699
Credit: 22,597,832
RAC: 0
    
Message 5954 - Posted: 8 Jan 2017, 16:32:51 UTC - in response to Message 5952.

Have no app_config.xml.

Erich,

you ignored this statement, so he can't have run them simultaneous

Erich
Send message
Joined: 18 Dec 15
Posts: 253
Credit: 1,942,248
RAC: 0
    
Message 5955 - Posted: 8 Jan 2017, 16:46:25 UTC

oh yes, sorry; you are right.
Also, this explains how he could do with the 3 GB disc limitation in the BOINC settings.

Message boards : Number crunching : Notebook w/ 4GB RAM - "waiting for memory"