| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: OET not selected, but work being sent. |
| 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 |
I have started getting credit for OET work units,
even though I have not selected OET. - Available Projects Participate in All Projects Outsmart Ebola Together ⢠Please review the system requirements before opting to participate in this project Uncovering Genome Mysteries Mapping Cancer Markers The Clean Energy Project - Phase 2 ⢠Please review the system requirements before opting to participate in this project [Selected] FightAIDS@Home Please note: Some projects may occasionally have periods where no work is available. If you choose to receive work for only one project, the project may, at times, not have work units available for download. For this reason, we recommend that you select more than one project. [Selected] If my computer can process work on my graphics card, then please send me work to run on my graphics card for the projects that I have selected above. [Selected] If there is no work available for the project(s) I have selected above, please send me work from another project. Please opt me in to new projects as they become available. - I have plenty of FA@H work units in cache. How are the OET work units being sent anyway? |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges: 
|
The reason you are getting the occasional OET1 WU is because you have this selected:
----------------------------------------[Selected] If there is no work available for the project(s) I have selected above, please send me work from another project. Please opt me in to new projects as they become available. If you unselect this you should not get any more OET1. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The reason you are getting the occasional OET1 WU I have plenty of FA@H work units in cache.is because you have this selected: [Selected] If there is no work available for the project(s) I have selected above,please send me work from another project. If you unselect this you should not get any more OET1. How are the OET work units being sent anyway? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There have been some incidences the last few days where one or the other prime selection was unavailable, then anything available is send at the moment of fetch request [if that option was selected]. Getting an OET this route is a rarity I'd say, per uplinger next to zero chance, given the major draw on the limited OET work supply, not 5% of total feeder occupation.
----------------------------------------P.S. There was talk that the project distribution was going to rebalanced, plus FAHV runtimes being extended [more work]. The drop off of the AutoDock work for FA@H is part of the supply gap at this time. [Edit 1 times, last edit by Former Member at Feb 13, 2015 2:43:04 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here latest impression of how work is weighing in at this time... MCM is far ahead of all others.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"at the moment of fetch request"
----------------------------------------I thought so. What's already in local cache is not considered. It maybe should be. Only send alternate work if local cache is empty of preferred work. Otherwise, "no work available" is False, but alternate work gets sent anyway. Someone in QA didn't catch this before shipping the code. [Edit 1 times, last edit by Former Member at Feb 14, 2015 5:32:02 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"Only send alternate work if local cache is
empty of preferred work." Actually that was proposed by undersigned 2 years or longer ago, not to sent alt work until some resource goes idle, and knreed would look at it. It required a "Preferred IP > 0" test or the like. Still all for it, downside, the client keeps asking and asking, so back-offs need to be increased. There's one snag in the story. If you also crunch elsewhere, the client will go there to fetch work. A full zero back-up project with zero resource/project weight only provides work when, yes, any resource goes idle.  |
||
|
|
|