| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Drug Search for Leishmaniasis Forum
Thread: Strange "running order" of DSFL jobs |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 22
|
|
| Author |
|
|
joeperry39@gmail.com
Advanced Cruncher USA Joined: Nov 22, 2006 Post Count: 140 Status: Offline Project Badges: 
|
I am suddenly seeing something very strange with the order in which my DSFL jobs are running. (As an aside -- I just installed a new HDD and the Boinc software, so in one sense started over from scratch)
----------------------------------------I started running 4 DSFL jobs (quad-core computer) and, after they ran for a while, stopped running in mid-job and 4 more WUs started running "High Priority." After that group of 4 WUs ran for a while, they too stopped and were replaced by 4 more WUs, again running in a "High Priority" status.  Has anyone had anything similar to this happen before? My other computer (dual-core) is running as usual with nothing happening out of the ordinary.    "Everything in moderation, including moderation" -- Mark Twain |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Do the run times look normal, inflated for that system?
What is the cache size setting? Do these tasks all have a 10 day deadline? Is the CPU running at normal max cycles? And related to previous question: Does the client benchmark show *normal* values after your new install? And of course, what client version did you choose to install? A few question to keep you busy ;>) --//-- |
||
|
|
martin64
Senior Cruncher Germany Joined: May 11, 2009 Post Count: 445 Status: Offline Project Badges: 
|
...and one more question: What is the setting for "Switch between applications every X minutes"? Try to set that to e.g. 5 minutes...
----------------------------------------Regards, Martin  |
||
|
|
joeperry39@gmail.com
Advanced Cruncher USA Joined: Nov 22, 2006 Post Count: 140 Status: Offline Project Badges:
|
Do the run times look normal, inflated for that system? What is the cache size setting? Do these tasks all have a 10 day deadline? Is the CPU running at normal max cycles? And related to previous question: Does the client benchmark show *normal* values after your new install? And of course, what client version did you choose to install? A few question to keep you busy ;>) --//-- Run times are actually faster since reload. Cache size setting is 3 days of extra work Yes, Deadline is 10 days Benchmark values appear to be very normal BOINC version is 6.10.58 OS is Win-7 Professional, 64-bit -- same as before re: Martin64 ...and one more question: What is the setting for "Switch between applications every X minutes"? Try to set that to e.g. 5 minutes... I had that set at 6000 minutes, same as before. Actually, all of my settings were picked up from my User ID when I logged back into the system after reloading BOINC. Therefore everything should be running the same, but it sure looks strange at this point. I did reset it to 5 minutes per your suggestion; we'll see if that makes any difference now or in the future. "Everything in moderation, including moderation" -- Mark Twain |
||
|
|
joeperry39@gmail.com
Advanced Cruncher USA Joined: Nov 22, 2006 Post Count: 140 Status: Offline Project Badges:
|
Do the run times look normal, inflated for that system? What is the cache size setting? Do these tasks all have a 10 day deadline? Is the CPU running at normal max cycles? And related to previous question: Does the client benchmark show *normal* values after your new install? And of course, what client version did you choose to install? A few question to keep you busy ;>) --//-- Run times are actually faster since reload. Cache size setting is 3 days of extra work Yes, Deadline is 10 days Benchmark values appear to be very normal BOINC version is 6.10.58 OS is Win-7 Professional, 64-bit -- same as before re: Martin64 ...and one more question: What is the setting for "Switch between applications every X minutes"? Try to set that to e.g. 5 minutes... I had that set at 6000 minutes, same as before. Actually, all of my settings were picked up from my User ID when I logged back into the system after reloading BOINC. Therefore everything should be running the same, but it sure looks strange at this point. I did reset it to 5 minutes per your suggestion; we'll see if that makes any difference now or in the future. And now this is getting more weird by the moment. Of the four jobs that were running as "high priority" one finished and has been reported. The other three shut down and now four new jobs in the list are running, again "high priority." This is getting stranger by the hour.  edit: Currently four jobs are running "high priority" and 11 are waiting to restart. I have "suspended" all of the other jobs that have yet to start in the hope I can force the jobs that were already started but not completed to resume processing. I'll post the results. "Everything in moderation, including moderation" -- Mark Twain [Edit 1 times, last edit by osugrad at Dec 7, 2011 1:08:26 AM] |
||
|
|
HutchNYC
Advanced Cruncher United States Joined: Nov 27, 2005 Post Count: 97 Status: Offline Project Badges: 
|
Are your bios and os clock times set properly? That could possibly cause the "high priority". Just a thought.
---------------------------------------- |
||
|
|
joeperry39@gmail.com
Advanced Cruncher USA Joined: Nov 22, 2006 Post Count: 140 Status: Offline Project Badges:
|
Are your bios and os clock times set properly? That could possibly cause the "high priority". Just a thought. Reset to NIST atomic clock earlier today. "Time" is most likely not the problem. "Everything in moderation, including moderation" -- Mark Twain |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am suddenly seeing something very strange with the order in which my DSFL jobs are running. (As an aside -- I just installed a new HDD and the Boinc software, so in one sense started over from scratch) It sounds like BOINC is running in "panic mode" (but don't ask me to explain that). If you have just downloaded a new set of tasks, they will all have similar Report Deadlines. I've seen that trigger the panic. BOINC will probably behave normally once the Report Deadlines are spread out after completing the start-up set of tasks and you have new downloads. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
System date right is important. If that work was fetched with a wrong system date and it then moved forward it could also have kicked this off [the inflated switch time wont have helped the situation]. Abort all unstarted jobs, reduce cache to 1 day and let it run a few days. If it does not right itself, check in again.
--//-- |
||
|
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18665 Status: Offline Project Badges:
|
If you prefer not to abort your unstarted jobs and given that system date has not been wrong for any time during or after getting WU's you have, resume any suspended jobs, go into Advanced-Preferences on the machine(s) in question and set the "Switch between applications every N minutes" to a very large value like 18000.0 (this overrides your profile setting on just that machine) and just give the machine time to clean up. BOINC 6.10+ will behave this way when you have more than about 3.5-5 days of WUs in your queue whether from the same project (WCG) or multiple projects. Setting that value high will force BOINC to work on oldest first. Once all your incomplete WUs are done, go back into Advanced-Preferences and hit Clear to set that machine back to your profile settings for BOINC.
---------------------------------------- |
||
|
|
|