Hello,
Since I update to Boinc client 7.0.25, now 7.0.27, my Windows XP 64bits hosts seems to never get anymore CPU tasks...
On the Boinc client, I reset my minimum work to 5 days + 0.1 day reserve.
I didn't change my Einstein's prefs.
But, in the Boinc log, I notice this new remark: "no work sent, see scheduler log on ..."
So I follow the link for the host log, and there, some parameters seem weird to me and I don't know how to fix that.
[send] CPU: req 0.00 sec, 0.00 instances; est delay 0.00 [send] CUDA: req 440640.00 sec, 1.00 instances; est delay 0.00
The client seems to only ask for GPU work.
[version] Don't need CPU jobs, skipping version 113 for einstein_S6LV1 (SSE2) [version] Don't need CPU jobs, skipping version 23 for hsgamma_FGRP1 ()
Why it's so? Why wouldn't it need CPU jobs???
[version] parsed project prefs setting 'also_run_cpu' : true : 1.000000 [version] project prefs setting 'also_run_cpu' (1.000000) prevents using plan class.
This one is super tricky for me to understand...
I try to set/unset this into Einstein's prefs: no change. No work is sent.
In my understanding 'also_run_cpu' should be set to 'true/1', but on the pref's setting, if I quote "Run CPU versions of applications for which GPU versions are available", the resulting value of 'also_run_cpu' in the local xml file is 0???
I also resetted the project, since it's a common advice when moving to new client version, but with no change.
If my GPU is detected, but eventually lack what's needed for GPU tasks, why the scheduler doesn't ask for CPU tasks anymore?
Copyright © 2024 Einstein@Home. All rights reserved.
Can't get CPU tasks with client 7.0.27
)
Hi
You could tell your BOINC client to write out log messages about the CPU scheduling decisions: create a file cc_config.xml in the BOINC data directory with this in it:
[pre]
1
[/pre]
See http://boinc.berkeley.edu/wiki/Client_configuration for more debugging flags.
Cheers
HB
The numeric value coding of
)
The numeric value coding of "" is confusing, partly because of the oddities of how BOINC handles project-specific preferences and defaults, and partly because it is incorrectly named.
After unchecking the checkbox beside "Run CPU versions of applications for which GPU versions are available" and saving your preferences on the web page, you have to update the Einstein@Home project (preferences) on you Client. Did you do that? If not, try that.
BM
BM
But anyway, setting this
)
But anyway, setting this value to true or false would not explain no CPU task getting scheduled at all. It's just a setting that affects searches trhat support both GPU and CPU, like the BRP4 search. The Gravitational Wave search and the Fermi LAT gamma ray pulsar search both don't have GPU versions, so they should not be affected by this setting.
Cheers
HB
Hi, RE: You could tell
)
Hi,
Thx for pointing this out. In fact, before posting to Einstein's forum, I did my preliminary searches at Boinc's forum. There is a lot a talk about new scheduler... First thing I did was to create this cc_config.xml file with sched debug options in it.
What commonly comes back with the new scheduler is to leave it alone for a week or more (!!!) and let it decide "what's good to your host"!!! Huh, ok. But not so ok.
Even if I'm the first to promote that "common user" should let the client crunch and shouldn't dive into geek or skilled people configuration; even if I don't watch all week my hosts crunching; from time to time, when I check, I'm happy to see that all projects with available WU send them to my hosts. I also know that there always an adaptation period between major versions of Boinc's client, but since I crunch, nothing like that with absolut no response from projects while there's job available...
Since my first post, nothing from Einstein, but Albert@home send me 5 WUs! As they have the same config items in account_*.xml. By comparing and filtering the debug infos between Einstein and Albert, I think I get it. It was described in Boinc's forum.
The debug option give this (it's filtered for just Einstein@home"):
Numbers that I'm able to recognize are "targer work buffer", according to my work reserve settings: 5 days x 24h x 3600s = 432000; 0.1 day reserve = 8640s. Then the "saturated" amount of 472108.93 which slowly but surely goes down.
For Albert, as soon as this number goes below the "target work buffer", WU are sent:
Other projects continue to send more than twenty WUs at a time... So, with the settings about minimun work and minimum+reserve work, I'm wondering if the scheduler estimates that with projects having already sent 20 WUs, it is saturate of GLOBAL work, and don't ask for more jobs. Yeah ok, but what about other projects?!?
I don't understand yet if this new scheduler is as "fair" than with 6.x versions... Don't misinterpret my words: I'm sure that Boinc's developpers do care about equality between projects. But with previous versions, it seems that ALL project where getting jobs inside the work reserve settings. With this new one, it seems that EACH project threshold for getting jobs is the minimum days work reserve??? I would rather have understand this as: minimum work reserve for ALL projects? Wouldn't I?
So does it mean that it's better to set minimum work reserve to ONE day?
Cheers
Update for previous
)
Update for previous post...
Finally I really don't get it about the new scheduler, the minimum work reserve and the "saturate" notion...
I wondered what will happen if I add more work reserve, in order for the "target work buffer" value to be over the "saturate" amount calculated for Einstein. So I put 5.5 days work min + 0.5 days reserve.
And in the sched debug log, a few seconds after modifying the settings, we can see that the scheduler decided, to raise the "saturate" value for Einstein (from 473851 to 496902)... So Einstein stays "backoff"... In the meanwhile, raising the work reserve amount allow some OTHER projects to get WUs.
And I still have this message from Einstein server:
"no work sent, see scheduler log on ..." (on several hosts with client 7.0.2x)
Any idea is welcome!
Cheers
RE: And I still have this
)
And what does the scheduler log tell you? (We can't see it, since your computers are hidden.)
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Hi, RE: And what
)
Hi,
I copied extracts and show them in the first message of the post.
This comes from the link proposed by Einstein's server in the Boinc standard log.
But here follows the full version:
I still wonder why there's "cpu req(uest) 0s" and "don't need CPU jobs".
That's why I tried to explore the debug sched from client.
I really feel that the Boinc's scheduler don't ask for CPU job...
I even try to disable GPU in the cc_config.xml to be sure that it falls back for CPU jobs. But yet with no luck...
Following different leads, I test other settings and set my work buffer to min=0.20d and reserver=0.20d. No more high priority jobs, but still no job from projects which usually sent WU very regularly.
Cheers
RE: Hi, RE: And what
)
Your 256Mb 8600GT on host 4279374 doesn't have enough memory for the BRP4cuda32 class plan, and doesn't have new enough drivers for the BRP4cuda32nv301 class plan, even if it did, you'll then find it doesn't have enough memory for that app eithier,
Is your cache full of CPU work from other projects?
Claggy
Have you tries deselecting
)
Have you tries deselecting gpu tasks under Einstein preferences? Maybe this would try and "force" boinc to grab CPU tasks for this project.
RE: Maybe this would try
)
Not if the client isn't asking for them (as is the case).
Gruß,
Gundolf
[edit]That works if the client asks for both but the feeder doesn't have enough tasks ready to satisfy the request, as it often happens over at SETI.[/edit]
Computer sind nicht alles im Leben. (Kleiner Scherz)