Advanced search

Forums : News : New Server is Live
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Crystal Pellet

Send message
Joined: 12 Feb 13
Posts: 23
Credit: 360,222
RAC: 0
Message 20539 - Posted: 1 Nov 2015, 8:21:59 UTC - in response to Message 20538.  

But it seems they not accept reducing the CPU usage. I turned it to 66% to be able to play but boinc use still 100 %. Even if a new WU is started

It seems!

The execution cap for the VM is reduced to 66% and VBoxHeadless.exe is using less cpu.
But the VM processes are running at normal priority, so the user may experience some sluggishness.
ID: 20539 · Report as offensive     Reply Quote
Profile Marius
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 29 Jun 15
Posts: 470
Credit: 4,276
RAC: 0
Message 20540 - Posted: 1 Nov 2015, 22:39:35 UTC
Last modified: 1 Nov 2015, 22:39:45 UTC

For Windows users who find their computer becomes very slow while BOINC is running due to camb_boinc2docker not being low priority, if you get a chance I am curious if the workaround mentioned in comment 7 here works for you. It says:
When you first start virtualbox with no running VMs, set the priority of VBoxSVC to below normal. After you do this any sub process will be created with the same priority.
ID: 20540 · Report as offensive     Reply Quote
Profile Marius
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 29 Jun 15
Posts: 470
Credit: 4,276
RAC: 0
Message 20541 - Posted: 1 Nov 2015, 23:59:07 UTC

Just updated camb_boinc2docker to version 0.07 which includes,

  • Fixed a bug causing Mac OSX camb_boinc2docker jobs to die immediately and return a validation error
  • Fixed a bug causing some camb_boinc2docker jobs to hang at ~99% until a BOINC restart.


Please let me know if you still see either of the above problems with camb_boinc2docker v0.07.

ID: 20541 · Report as offensive     Reply Quote
Profile Marius
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 29 Jun 15
Posts: 470
Credit: 4,276
RAC: 0
Message 20557 - Posted: 3 Nov 2015, 22:04:08 UTC

Justed update camb_boinc2docker to version 0.08 which finally includes Docker 1.9.0 (released hours ago!)

This should get rid of problems people were having where the jobs were just getting stuck for a very long time at 0.100% (i.e. while the Docker image was being pulled), as well as jobs which terminated immediately and ended up invalid.

In a few days, if everything looks OK, I will remove the beta status of camb_boinc2docker and open it up to our much larger user base. If you still see problems with camb_boinc2docker now would be a good time to comment :)
ID: 20557 · Report as offensive     Reply Quote
Jim1348

Send message
Joined: 17 Nov 14
Posts: 86
Credit: 3,988,270
RAC: 1,457
Message 20559 - Posted: 3 Nov 2015, 22:21:47 UTC - in response to Message 20557.  

Thanks for the updates. You have made the Beta interesting (not always the case).
ID: 20559 · Report as offensive     Reply Quote
Jim1348

Send message
Joined: 17 Nov 14
Posts: 86
Credit: 3,988,270
RAC: 1,457
Message 20564 - Posted: 6 Nov 2015, 17:13:30 UTC - in response to Message 20540.  
Last modified: 6 Nov 2015, 17:21:37 UTC

For Windows users who find their computer becomes very slow while BOINC is running due to camb_boinc2docker not being low priority, if you get a chance I am curious if the workaround mentioned in comment 7 here works for you. It says:
When you first start virtualbox with no running VMs, set the priority of VBoxSVC to below normal. After you do this any sub process will be created with the same priority.

Yes, it works. I used Prio to set the process of VBoxSVC to "Low", but I had to do it while BOINC was running. Then I rebooted, and both VBoxSVC and all the three VBoxHeadless were also set to Low.

I need this to ensure that my GPUs run at full speed. Even though I reserve two CPU cores for them by using the app_info to set camb_boinc2docker to 6 cores, they still ran slowly. I am hoping the priority change will fix it, but at least it can be set now.
ID: 20564 · Report as offensive     Reply Quote
Jim1348

Send message
Joined: 17 Nov 14
Posts: 86
Credit: 3,988,270
RAC: 1,457
Message 20565 - Posted: 7 Nov 2015, 12:20:20 UTC - in response to Message 20564.  

If I read the release notes correctly, then both the "wrapper" priority and the GPU priority can be set by the latest BOINC (7.6.14), so the use of Prio should not be necessary in the future, but I have not tried the new BOINC yet.
ID: 20565 · Report as offensive     Reply Quote
Previous · 1 · 2

Forums : News : New Server is Live