Stange behavior of the BOINC Manager

Message boards : Questions and problems : Stange behavior of the BOINC Manager
Message board moderation

To post messages, you must log in.

AuthorMessage
Kokomiko
Avatar

Send message
Joined: 12 Apr 07
Posts: 7
Germany
Message 22767 - Posted: 30 Jan 2009, 0:57:39 UTC

Since BM 6.x I see a strange behavior of the Boinc Manager.

It looks, like the volunteers don't get longer the control over his own PC. Berkeley seems to overrule any intervention of the user to get more work for his preferred project by start and stop other projects (e.g. a competition). Only the percentage for a project can rule now the amount of work. Bu also this don't work trustworthy, so I get over 80 hours work for SETI although I've set SETI to no new work. Sameproblem I had with PrimeGrid, got so much work, that the PC start crunching in high priority mode.

My work buffer was set to 1 day, the work I got was for a Phenom II 940 more that he could crunch in 4 days.

Otherwise a project with high ressource share (500, all others together 200) got no new work. The BM 6.6.3 don't show the amount of seconds he is calling. That's not nice. I'm interested to know this. If the user isn't worth to get this information?

If this come true, many user will stop spending PC power for the science. No one like it, that he can't control what going on on his own PC.
There is anywhere one bug more ...
ID: 22767 · Report as offensive
Les Bayliss
Help desk expert

Send message
Joined: 25 Nov 05
Posts: 1654
Australia
Message 22770 - Posted: 30 Jan 2009, 1:33:10 UTC - in response to Message 22767.  

This is a known problem that the developers are trying to fix right now.
There's lots of threads about it on this site if you want to read about it.

In the meantime, it's best if you go back to 6.2.19, and wait for a fixed version.

ID: 22770 · Report as offensive

Message boards : Questions and problems : Stange behavior of the BOINC Manager

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.