1) Message boards : LHC@home Science : Problem with virtual box settings/configuration (Message 32493)
Posted 21 Sep 2017 by Iscaran
Post:
No it seems correct. As that is probably what happens with the LHC, ATLAS task in the VB.

Although the task itself is maybe reported as say 2500MB due to the fact it requires running in the VB it is "expanded" to something larger than that.

At the same time my BOINC is set to utilize maximum 90% RAM when idle. System has 4GB so 90% = 3600MB.

Now it decides 2500MB LHC Task is <3600MB Limit and kicks it off in the VB...but the VB which gets created "automatically" sizes to 3500MB (+ maybe some more excess) which then causes the system to cripple down as it has to shuffle data from and too the HDD Swap file all the time when trying to reawake.

So as I see it I can either "cripple" my BOINC by using a lower total RAM setting (say 50% instead of 90%) to avoid the BOINC manager to start too large virtual boxes which exceed the RAM limitation.
Or I choose not to run ATLAS and LHC tasks at all. Which seems to be the smarter option as the other task then can access 90% of RAM instead of just 50%.

BUT:
I think I tried using a global memory limit of as low as 50% already and still it kicked off virtual boxes which were set to 3500MB of RAM.
Anyway to know for sure I will try that today over night...lets see if I can get the system back tomorrow morning.

Also to consider:

WHY the virtual boxes still get created with 3500MB when I EDIT the .xml to use only 2048MB ?

EDIT: I created also a question on this on the BOINC board as you suggested:
http://boinc.berkeley.edu/dev/forum_thread.php?id=11866&postid=81522#81522
2) Message boards : LHC@home Science : Problem with virtual box settings/configuration (Message 32491)
Posted 21 Sep 2017 by Iscaran
Post:
Thank you.
No I didnt see Yetis post first. From reading through it I learn that LHC and ATLAS Task might be too large for a system with that limited amount of RAM as I have.

For the time now I have disabled LHC and Atlas tasks - since if the numbers are correct they would require >2GB RAM in the virtual box.

The Problem seems to be then that the BOINC Manager seems to be unable to properly limit the VBox RAM size to a reasonable amount(and thus would automatically skip task which are too large to fit in the box).
That way it should no longer happen that the system is not responding within a reasonable time after mouse movement.
3) Message boards : LHC@home Science : Problem with virtual box settings/configuration (Message 32488)
Posted 21 Sep 2017 by Iscaran
Post:
But shouldnt the BOINC client automatically detect that the VBox setting is too small and therefore NOT load such tasks on a machine like this ?

I mean I have set global pereferences properly before in the BOINC client.
For example I have defined that calculation stops when mouse is used and that the system is allowed to take up to 90% of the System RAM. (which would be 3600MB maximum).
This works pretty fine and the system returns into a responsive "workable" condition within a few seconds after moving the mouse.

Now with VB installed however there are no special global preferences for the VBox and it seems that when the system creates a VBox according to the global preferences it seems to overstretch the system somehow.

When I then try to return the system into "workable" condition when there is a default VB task by moving the mouse it can take up to 30minutes to respond.

When I wait that long and then open up the Vbox manager and edit the value of memory to be used into e.g. 2048MB instead of the 3500MB which are there. Then the returning into normal state is again "normal" (within a few seconds).

But OK I can disable ATLAS and LHCb tasks then completely if they require that large amounts of Memory for VBox.

Also there is nowhere an information on how much RAM which tasks require...could be helpful to add this to the selection in the account management or in the global settings ?
4) Message boards : LHC@home Science : Problem with virtual box settings/configuration (Message 32484)
Posted 21 Sep 2017 by Iscaran
Post:
Hello All,

recently I upgrade to the new BOINC client and decided to also use the virtual box installation (Host-System is a Win7 x64).

BOINC is set to run only when system is idle and recently I am running in to issues that waking the system up again is often hardly possible.

Now I find that the created virtual boxes (VB) always start with 3500MB of memory setting. This is a problem because the Host only has 4GB total RAM and thus when I try to re-awaken the system it takes like 30min before it actually gets "usable" again as it seems the VB is eating up all the memory and it takes that long to "clean" it up.

When I manage to set the running VB to 2048MB memory allocation then wait until the system goes into BOINC-state and try to re-awaken it works fast (within a few seconds).

Now the problem is - that whenever a new task is applied it creates a new VB and it has AGAIN the default setting of 3500 MB RAM.

I already edited the projects xml e.g. \BOINC_Data\projects\lhcathome.cern.ch_lhcathome\ATLAS_2017_01_09.xml

so it reads 2048 MB
<memory_size_mb>2048</memory_size_mb>

But still whenever e.g. an ATLAS task is startet the VB starts with 3500MB allocation...

So my question is, how and where can I change the default value with which VBs for the calculation task are created. And how can I make sure the setting is not overridden somehow ?

I hope somebody can help me with this issue, otherwise I will have to go back to the defaul client with no VB.



©2024 CERN