This conversation confused me, until I looked at the actual format of a
sched_reply.xml file.
<project_preferences>
<resource_share>100</resource_share>
<project_specific>
<format_preset>s...@home classic</format_preset>
<text_style>Pillars</text_style>
<graph_style>Rectangles</graph_style>
<max_cpu>50</max_cpu>
<grow_time>10</grow_time>
<hold_time>5</hold_time>
<graph_alpha>0.7</graph_alpha>
<roll_period>10</roll_period>
<roll_range>20</roll_range>
<pitch_period>30</pitch_period>
<pitch_range>30</pitch_range>
<starfield_size>2000</starfield_size>
<starfield_speed>40</starfield_speed>
<color_preset>Rainbow</color_preset>
<start_hue>0</start_hue>
<hue_change>1</hue_change>
<app_id>2</app_id>
<app_id>3</app_id>
<app_id>4</app_id>
<allow_non_preferred_apps>1</allow_non_preferred_apps>
<no_gpus>1</no_gpus>
</project_specific>
</project_preferences>
So, the information is indeed being passed back and forth, but in the wrong
place.
Would it not be better to define a standard set of *BOINC* tag names:
<use_CPU>0|1
<use_nvidia_GPU>0|1
<use_ATI_GPU>0|1
...
and pass them in the outer <project_preferences> group (with resource share),
and not in the inner <project_specific> group? Then they *would* be parsed, and
*could* be used in work fetch decisions.
At the moment, these values are set on a project preferences web page which
states "Client-related preferences will take effect when your computer
communicates with s...@home or you issue the "Update" command from the BOINC
client." - which is untrue for these preferences, which to my eye are indeed
client-related.
This subject - "I've set Use Central Processing Unit (CPU) to 'no' on the
website, why does my client keep asking for CPU work?" - keeps cropping up on
project message boards, and it's becoming increasingly difficult to compose a
logical reply which doesn't cause offense to the questioner.
On Sep 25, 2009, at 9:35 PM, Nicolás Alvarez wrote:
>> Oh, and if the BOINC client knows that I don't want MW CPU tasks, why
>> does it keep asking for them ... I am on the third iteration already
>> when oh when is it going to ask for GPU work like my preferences
>> state?
>
> Because they are "project-specific preferences", which have project-
> specific
> syntax and meaning. The client doesn't even parse them. The client
> *doesn't*
> know that you don't want MW CPU tasks. It only knows that there are
> project-specific prefs saying "<gpu>0</gpu>" (or whatever) and
> passes them
> back and forth on the project and to the science apps (since there
> could be
> things like screensaver prefs in there), *without* parsing them.
Following that logic then the BOINC client could and should not use or
interpret the Resource Share which is set on that same page.
But the BOINC client does read RS and does use it, however
ineffectually, so your argument is without merit ... sorry ...
I grant that the client is not looking at it ... but that is a design
and implementation flaw ...
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
