| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
Kinwolf
Cruncher Joined: Feb 22, 2011 Post Count: 11 Status: Offline Project Badges:
|
Ever since I decided to give some CPU time to another project(SETI@home) Boinc is behaving strangely.
Instead of computing 3 WU from whatever application, it now will start 3 WU, then stop and start other WU, then stop, go back to 1 or 2 previous WU while starting a new one... The end result is that I now have 8 WU started, 6 from Human protenome, one form SNTS and one from SETI, none finished, and it it still starting new ones!! One unfinished WU from HPFP2 has been sitting there for the last 24 hours! How can I prevent this and force it to finish it's already started WU instead of starting new one that are from the same application? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Except for changing the switch time "
----------------------------------------With multiple grids attached to a client and active and each having different deadlines and runtimes, that's what to expect, in a nutshell, SAN. edit: ** Well there is the micromanaging way, manually suspending and releasing tasks, which often makes matters worse, plus, if a task of a project [any of WCG e.g.], then the work fetch is suspended for that project [Maybe not a bad thing if tasks are under deadline threat] ;>) edit: Brain-Fingers disconnnect typo [see post Scribe 3rd from top] [Edit 2 times, last edit by Former Member at Jun 12, 2013 3:42:31 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ever since I decided to give some CPU time to another project(SETI@home) Boinc is behaving strangely.......... .....of course the simple answer could be SETI.....you have found alien life and you are infected.... ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
....and the other thing I would do is set the "Switch between applications every" setting to something like 10,000 minutes which should mean you finish a WU before swapping applications.
![]() |
||
|
|
Kinwolf
Cruncher Joined: Feb 22, 2011 Post Count: 11 Status: Offline Project Badges:
|
Thanks for all the infos.
I'll try the "Switch between applications every" settings to see if it helps. |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges:
|
If this will not help, upgrade BOINC to version 7.0.xx. AFAIK, the problem you are mentioning used to affect users with BOINC version 6.xx.yy
----------------------------------------Cheers ![]() ETA: is it something similar to David Autumns' problem we discussed here? ![]() Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006 ![]() [Edit 1 times, last edit by branjo at Jun 12, 2013 5:17:40 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That problem... hmmm, what exactly was that problem, supposedly fixed in 7?
|
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
That problem... hmmm, what exactly was that problem, supposedly fixed in 7? v6.10.xx has seriously screwed-up handling of deadlines and high priority. For the early versions like 6.10.1x - v6.10.2x you could easily have 100+ partially-crunched tasks for the same project, but thankfully this was atleast improved in the later clients. But, another bug never fixed in v6.10.xx is, even if a task was in deadline-trouble, and even if the deadline was passed, the client could instead choose to run work for another BOINC-project with 1+ month until the deadline and with no deadline-problems. ![]() "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
|