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: 7
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi experts,
i have a strange issue in my thougths. I got now around 30 new files in one session with a remaining time of 00:53:24 for each file. But when the calculation starts it says around 6 to 7 hours remaining time. All the files are for FightAIDS@Home and they have all the deadline until 11/02/2017 06:55:45 and this is not to do because i have much more projects. As Sample SETI@home. I use the latest BOINC client (7.6.33 x64) on three machine (W7 Ultimate, W7 Pro, W10 Pro). The World Community Grid files are running on the W7 Pro machine. That machine is my main one for coding and texting. I have never seen that issue with SETI@Home files. - Is someone in state to describe me whats going on? - I that normal? - For more information about the system or client settings please ask me. With that issue i can't do any work for SETI because the deadline. |
||
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2195 Status: Recently Active Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Same problem as here: https://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=538384
----------------------------------------To solve your problem, you could uncheck doing work for FightAIDS@Home (there are more than enough other people to crunch FightAIDS@Home ![]() [Edit 2 times, last edit by adriverhoef at Feb 3, 2017 10:16:19 AM] |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7745 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
For the Fight Aida@Home project, they are putting out two different types of work units. Some are for flexible ligands and some for rigid ligands. They vary widely in how long they take to complete. The BOINC software has trouble with these widely varying completion times because if the machine has been running the short ones, it attempts to keep your queue full with those, but if it suddenly loads the longer ones, you will be over committed. You could just shorten your queue or opt out of this project.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
First thanks for answers..
I think i will test the advise from Sgt. Joefirst and will report later in some ;-) Sgt. Joe: You said it's an issue with BOINC client. May i aask which client you are using? |
||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7745 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I use Boinc 7.4.7 (WCG version) for my Windows machines. On my Linux machines I have several different versions depending on when I started the machine. If it is stable when I started, I just leave it alone and let it run.I don't think this issue is version specific, but is a consequence of the scheduling algorithm within BOINC trying to balance the queue while doing work units of widely varying lengths (which can be problematic.)
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For the Fight Aida@Home project, they are putting out two different types of work units. Some are for flexible ligands and some for rigid ligands. They vary widely in how long they take to complete. The BOINC software has trouble with these widely varying completion times because if the machine has been running the short ones, it attempts to keep your queue full with those, but if it suddenly loads the longer ones, you will be over committed. You could just shorten your queue or opt out of this project. Cheers emphasis mine, No, the server has trouble in headering new work with proper FPOPS, where Rigid and the rest have 2 entirely different runtime ranges. The client has little issue, WCG made it to have lots of trouble by disabling the DCF function, so it can sense true runtimes for the Rigid and adapt work requesting, so I've resorted to rebuilding making it oblivious to <dont_use_dcf/>, might even spend time on re-developing code to give each app it's own DCF [re-developing, because the code/client was already created years and years ago, but not boarded by Berkeley... was it offered, was it rejected, not privy to the history, so it only exists in privately build distribution in an older client compile, but it is THE answer for umbrella projects like WCG]. Not my problem anymore. See ya later. PS WCG has a solution in hand [where's a will, there's a way]... random mix Rigid and shorts in the distributor, and eventually over time a reasonable mean would percolate out, which is somewhere over 2 hours according the WCGART chart. |
||
|
awilddog
Cruncher Joined: Jan 12, 2008 Post Count: 1 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
One of the problems with remaining time is it is incorrectly computed in all projects.
(Elapsed_time/%progress) - elapsed_time = remaining time; This computation will give the exact remaining time. Currently an guess for total time is set when the unit of work is sent. If you watch remaining time, it decrements by seconds, then by some large value when the work unit is almost done. |
||
|
|
![]() |