Message boards :
Number crunching :
Stuck at 100%
Message board moderation
Previous · 1 · 2 · 3
Author | Message |
---|---|
Send message Joined: 12 Aug 06 Posts: 418 Credit: 5,667,249 RAC: 3 |
I've noticed that although my config file says 5GB, that's it's still using 4.2GB for 2C and 5.8GB or the 3C (if you believe the "working set size" in the task's properties). Seems to be making it work though.... |
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,569,815 RAC: 10,128 |
I've noticed that although my config file says 5GB, that's it's still using 4.2GB for 2C and 5.8GB or the 3C (if you believe the "working set size" in the task's properties). Seems to be making it work though.... Settings in app_config.xml don't affect "working set size", but memory settings inside the VM Supporting BOINC, a great concept ! |
Send message Joined: 28 Sep 04 Posts: 675 Credit: 43,647,526 RAC: 15,922 |
I've noticed that although my config file says 5GB, that's it's still using 4.2GB for 2C and 5.8GB or the 3C (if you believe the "working set size" in the task's properties). Seems to be making it work though.... Which means that you can not trust Boinc to control used memory correctly if you want to reserve some memory for programs running outside Boinc. |
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,569,815 RAC: 10,128 |
Which means that you can not trust Boinc to control used memory correctly if you want to reserve some memory for programs running outside Boinc. Nope The Scheduler sets the "WorkingSetSize", but the app_config.xml may override this on the client. So, "WorkingSetSize" is a clear defined value that always can be calculated. You are changing / overriding the config with the app_config and now it is your responsibility to keep an eye on the memory. Supporting BOINC, a great concept ! |
Send message Joined: 15 Jun 08 Posts: 2411 Credit: 226,413,729 RAC: 131,878 |
A deeper explanation regarding working set size and rsc_memory_bound can be found in the BOINC wiki: https://boinc.berkeley.edu/trac/wiki/MemoryManagement It also explains (section: Client CPU scheduler) why sometimes a "waiting for memory" situation occurs. |
Send message Joined: 28 Sep 04 Posts: 675 Credit: 43,647,526 RAC: 15,922 |
A 2 core Atlas task is running on my computer now and the Working set size in Boinc is showing 5300.00 MB. So this is good. |
Send message Joined: 12 Aug 06 Posts: 418 Credit: 5,667,249 RAC: 3 |
Should I eventually remove the config.xml I created as instructed above, once the programmers correct the error? Otherwise it'll prevent any changes from the server side? |
Send message Joined: 27 Sep 08 Posts: 807 Credit: 652,392,545 RAC: 282,294 |
If you set your web config to 3cores, then the working set size in boinc will be 5GB, you could try 4 core on the web. The calculation for the web 2.6 GB + N * 0.9 GB. (it waas just updated) Since you have an app_config it's just for BOINC's calacualtions. They will make some changes as per discussion in the other threads |
Send message Joined: 12 Aug 06 Posts: 418 Credit: 5,667,249 RAC: 3 |
f changes are be5ng 0ade, '33 d5sab3e the c6nf5g f6r n6w and see 5f the s c60-3ete -r6-er3y Wthey were fa535ng after 1* 05n4tes bf6re* ARGH! Numlock left on! If changes are being made, I'll disable the config for now and see if the WUs complete properly (they were failing after 10 minutes before). |
Send message Joined: 6 Jan 16 Posts: 1 Credit: 1,612,562 RAC: 1,311 |
I have the same thing lot of times. It begin well then at the end it indicate something like 30 seconds remain the an hour after 29 secondes then one our after 28 etc. to 0 secondes then the limit date pass over and the task still take CPU. So if I understand what has been said my computer worked for nothing rather than using power for an other project. Could you fix it a the LHC@Home project ? when it fails then stop it and get back the result. Yes it's Atlas. |
©2024 CERN