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: 9
|
![]() |
Author |
|
Nortnarg
Senior Cruncher U.S.A. Joined: Nov 23, 2007 Post Count: 184 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
To offset some of the slowdowns/shutdowns, I set the cache to 5 days. No extra work units are being downloaded. Only what is actively running. Anyone else seeing this?
----------------------------------------![]() |
||
|
bfmorse
Senior Cruncher US Joined: Jul 26, 2009 Post Count: 302 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
You might want to re-evaluate that.
RESEND WU’s typically only have a 2 - 3 day deadline and that deadline would expire before you planned on running that WU. Which, in turn would generate another RESEND and potentially mark YOUR WU as TOO LATE. I would recommend that you consider a 1.0 to 1.4 day queue. That way you have some reserve but not so much as to cause WU’s timing out that have been assigned to you. I have chosen to run a 0.05 day queue. But, you do not need to be that cautious. Happy Crunching! |
||
|
Nortnarg
Senior Cruncher U.S.A. Joined: Nov 23, 2007 Post Count: 184 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Maybe that is the issue I will try a lesser time
----------------------------------------![]() |
||
|
Nortnarg
Senior Cruncher U.S.A. Joined: Nov 23, 2007 Post Count: 184 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Maybe that is the issue I will try a lesser time I set to 1 day and having the same issue. Not the end of the world here of course, just wondering if this function still works with WCG. RG ![]() |
||
|
BobbyB
Veteran Cruncher Canada Joined: Apr 25, 2020 Post Count: 609 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() |
You have to consider that there are many (of us) who are also trying to grap a WU and if there are none there are none. So no matter how much or little you set the cache at there will be none coming in. I'm presuming these are fast machines. Two old laptops I also have never run out just because they are not fast enough to eat up all the WUs in the cache.
----------------------------------------Check your logs with BOINC Manager and you will see that WCG checks very often for work. My solution for not having an idling machine to to also have another project running like Tn-Grid which now has work. [Edit 1 times, last edit by BobbyB at May 19, 2023 4:27:27 PM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7691 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
RESEND WU’s typically only have a 2 - 3 day deadline and that deadline would expire before you planned on running that WU. Which, in turn would generate another RESEND and potentially mark YOUR WU as TOO LATE. BOINC has a built in mechanism to start tasks which have a closer deadline than other tasks in the queue. This does work marvelously well unless, of course, if your queue is grossly overproviosioned. Generally speaking, a 2-3 queue is not overdoing it. Most people probably should just observe how BOINC handles the number of items in the queue along with the speed and activity of the machine. Starting fairly small and making small adjustments either up or down should provide for not missing any deadlines and yet maintaining a supply so you don't run dry. Of course, if the supply gets cut off or is otherwise constrained, some instances of running dry will occur. If the supply of work units remains stable and the average length of the work units remains within reason limits, this should work fine over time. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Taurus Oldbull
Advanced Cruncher US Joined: Nov 26, 2020 Post Count: 53 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() |
"BOINC has a built in mechanism to start tasks which have a closer deadline than other tasks in the queue. This does work marvelously well unless, of course, if your queue is grossly over-provisioned."
On my Mac, BOINC has always sequenced the execution of tasks in the order in which they were received, regardless of the deadline. Is the order of execution a configurable parameter? |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7691 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
On my Mac, BOINC has always sequenced the execution of tasks in the order in which they were received, regardless of the deadline. Is the order of execution a configurable parameter? Not to my knowledge. Also, I don't own a MAC so I do not know what their idiosyncrasies are. I vaguely recall some forum post from Ingleside years ago which had a pretty good explanation of how that feature in BOINC works. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
![]() |