Advanced search

Message boards : Technical Support : Taking a break from Cosmology@home

Author Message
pe
Volunteer tester
Send message
Joined: 21 May 07
Posts: 2
Credit: 1,089,968
RAC: 70
Message 21279 - Posted: 12 Jan 2017, 21:50:53 UTC

Hi there,

just wanted to inform you that I need to take a break from crunching for Cosmology@home. Doing work for this project does leave my computer more or less unusable.. since I only crunch while using my computer, this is no longer tolerable. And it won't be that great of a loss for the project either :) no power-farms here.

It is funny that this project seems to break my machine while all the others are running fine.. even those needing more resources. from what I can tell the problems did start with the multicore non vbox application, and it did not get better since.

Just wanted to let you know that there are some serious performance issues.
I will try doing some work from time to time to see if there are any improvements.

Keep up the good work and good luck for the project!
Best regards,
p.
____________

Profile Marius
Project administrator
Project developer
Project scientist
Avatar
Send message
Joined: 29 Jun 15
Posts: 427
Credit: 4,276
RAC: 0
Message 21280 - Posted: 12 Jan 2017, 23:39:23 UTC - in response to Message 21279.

Hi pe, appreciate your contributions and sad but understand the decision to leave.

The performance issue you're describing is most likely this one, unfortunately caused by a bug in Virtualbox which is completely out of our control. As mentioned in the link, a partial workaround is to limit the number of cores used by the camb_boinc2docker app. If you leave at least one core completely idle, or even in use but crunching non-vbox apps, that should still keep your computer responsive.

Anyway, we will certainly post once that problem is solved on the VBox end.

pe
Volunteer tester
Send message
Joined: 21 May 07
Posts: 2
Credit: 1,089,968
RAC: 70
Message 21283 - Posted: 14 Jan 2017, 22:32:05 UTC - in response to Message 21280.

Hi Marius,

thank you for the answer.
Actually I already tried the solution in the linked thread some time ago: it does not work for cosmology@home on my system.
As soon as I have this vbox-app running, the performance goes down. I know that there was at least one core for a non-vbox app, but I need to check again if it is the same if no other vbox is running or not.

I know found out that there are other vbox apps which also cause performance issues on my system when running simultaneously to other vbox apps (even with at least 1 core left for anything else). Those performance issues are not nearly as bad as those from the cosmology vbox, and it seems to be only temporary while with cosmology it is all the time the vbox is running.
Then there are other vbox apps which do not cause performance issues at all, even when running simultaneously. So from my experience those performance issues are indeed app-dependent.

Does anyone know how to configure boinc to only run 1 vbox app at a time - across all projects? I can limit the instances per app/project, but that does not stop boinc from running a vbox from another project :)

thank you and best regards,
pe.
____________

GARY
Send message
Joined: 30 Jun 09
Posts: 1
Credit: 1,098,074
RAC: 1,634
Message 21503 - Posted: 30 Aug 2017, 19:28:35 UTC - in response to Message 21280.

Hi pe, appreciate your contributions and sad but understand the decision to leave.

The performance issue you're describing is most likely this one, unfortunately caused by a bug in Virtualbox which is completely out of our control. As mentioned in the link, a partial workaround is to limit the number of cores used by the camb_boinc2docker app. If you leave at least one core completely idle, or even in use but crunching non-vbox apps, that should still keep your computer responsive.

Anyway, we will certainly post once that problem is solved on the VBox end.

____________

Message boards : Technical Support : Taking a break from Cosmology@home