Ignoring request for no GWO2 GPU work units

Ron Kosinski
Ron Kosinski
Joined: 23 Mar 05
Posts: 57
Credit: 898941156
RAC: 644393
Topic 222462

Einstein is ignoring my request not to receive 2.07 GWO2 GPU work units on one of my computers.  I have un-checked the box in Project Preferences under Home location and the computer is set to Home location.

Jonathan
Jonathan
Joined: 4 Oct 17
Posts: 15
Credit: 16939851
RAC: 552

Try exiting Boinc and all

Try exiting Boinc and all tasks on that computer and start Boinc up again.  Watch your logs to see it got updated preferences

Ian&Steve C.
Ian&Steve C.
Joined: 19 Jan 20
Posts: 3720
Credit: 34824886399
RAC: 31676836

did you also set this to

did you also set this to "No"?

Allow non-preferred apps:
If no work for selected applications are available, accept tasks from other applications?

_________________________________________________________________________

Ron Kosinski
Ron Kosinski
Joined: 23 Mar 05
Posts: 57
Credit: 898941156
RAC: 644393

Ian&Steve C. wrote:did you

Ian&Steve C. wrote:

did you also set this to "No"?

Allow non-preferred apps:
If no work for selected applications are available, accept tasks from other applications?

I did not.

I will do that.

Will that affect anything else?

Ian&Steve C.
Ian&Steve C.
Joined: 19 Jan 20
Posts: 3720
Credit: 34824886399
RAC: 31676836

no, it just enforces that you

no, it just enforces that you will only get work for the apps you've selected.

_________________________________________________________________________

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5850
Credit: 110140605996
RAC: 25769594

Ron Kosinski wrote:Will that

Ron Kosinski wrote:
Will that affect anything else?

You might be wondering why you needed to do this in addition to having deselected that GW search.  You would be excused for thinking that not having the search selected should be sufficient on its own.

The explanation (given years ago) is something like the following.  The available tasks for the FGRPB1G search exist in two separate groups.  There is a small 'rapid response' cache of work that the scheduler can immediately access.  There is a second, much larger (and slower) group that the workunit generator keeps topped up when necessary.  If the small cache gets depleted quickly (lots of requests), there is a small time window until another background process wakes up and transfers a new batch from the large second group into the rapid response group.  If you happen to make a work request during that small window, the scheduler will (momentarily) have no available 'preferred' work and will therefore look at your setting for 'non-preferred' work.

By setting that to 'NO', your client will get a 'no work available' message but will then (60 secs later) repeat the request, by which time the rapid cache will have been refilled.  So, if you only ever want work for preferred apps, you really need to have that setting on 'NO'.  At the moment, with the surge in demand, it's probably more common for people to 'hit' that small 'window of opportunity' and be allocated non-preferred work as a result.

Cheers,
Gary.

Ron Kosinski
Ron Kosinski
Joined: 23 Mar 05
Posts: 57
Credit: 898941156
RAC: 644393

I want to thank everyone for

I want to thank everyone for their help in this matter.  It was greatly appreciated.  Setting the "Allow non-preferred apps" to "No" did the trick.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.