Ignoring settings to avoid CPU WUs
17 May 2020 15:31:35 UTC
Topic 222519
(moderation:
I keep getting CPU WUs for the Gamma-ray pulsar search #5 named LaTeah. I don't want 'em. I've got my CPU busy doing other stuff, like Rosetta and WCG tasks. My GPU is free game though, bombard that bad boy all you want as long as GPUGRID is out of work.
On Einstein's website, under project, I have the following settings. Use CPU is set to no. Use GPU is set to yes, as intended. Beta settings is set to yes (which may or may not be the reason it's getting CPU units, but these aren't beta ones I'm getting anway, so it's irrelevant). The only applications checked are the two GPU pulsar applications. #5 is not checked. Run CPU versions of applications for which GPU versions are available is set to no. Allow non-preferred apps is set to no. Default set: set used for new computers is set to no. Under computing, I have the following settings. Use at most is set to 100% of the processors 100% of the CPU time. This could explain why it's using the CPU, but could not explain why it's getting CPU units.
I've got local prefs set that override whatever I've got set on BOINCStats. Neither of those should have any bearing on what Einstein is doing since neither has granular control over CPU/GPU task preferences per project. I speculate that maybe what's happening is that Einstein isn't bothering to check the preferences on its own website first, and is skipping ahead to asking BOINCStats what to do. There's nothing in the event log to explain why this might be happening; the tasks just start showing up in the event log, same as anything else would without incident.
On a semi-related note, I get this in my event log. I'm just pasting this here in case it might be significant in talking about BOINCStats prefs versus local prefs versus project prefs.
11-May-2020 00:10:39 [---] General prefs: from https://bam.boincstats.com/ (last modified 05-Apr-2020 17:37:29)
11-May-2020 00:10:39 [---] Host location: none
11-May-2020 00:10:39 [---] General prefs: using your defaults
11-May-2020 00:10:39 [---] Reading preferences override file
If you'd like to fix the
)
If you'd like to fix the problem, I think the two most likely problems are these two:
1. Perhaps you are adjusting the preferences for a location (aka venue) which is not the location to which the system in question is assigned (home, school, etc.)
2. Perhaps the beta setting is the problem.
About the beta setting--it does override other settings appreciably, and I don't know the full scope. Further, I don't know a reliable way to determine that a task is not a beta task.
Anyway, what is your goal in choosing to accept beta work?
There's only 2 things I can
)
There's only 2 things I can think of that might cause this:
1. The allow beta setting. This has caused ignoring of application preferences on other occasions. Try setting it to no and then do a couple of updates/scheduler contacts and see if that stops the FGRP5 CPU tasks. You can always reset it to yes if it's not the cause.
2. The host location doesn't match the preference set. Make sure that your editing the right preference set, according to the event log your host location is set to "none" and that's the generic/default/---/none location. (It might have even more names!)
The Computing preferences shouldn't impact what tasks are downloaded, only how the already downloaded tasks are run.
I tried to check the server side log of the last contact from your computer but unfortunately it only contained a report of a finished task, no work request.
There are multiple ways of accessing this log, go to your Account and then either click on the computer name or on More beneath it. Then find the the date and time link and click it to see the log.
Gary has posted a guide to reading this log in the Getting started section that might help in deciphering it or you could post a copy if it's not to verbose.
Edit: Archae86 beat me to it!