There is still "O2MD1" work for the CPUs. However currently the "locality scheduler" only makes one pass per work request (GPU or CPU). if the client requests work for the GPU, it will (try to) send GPU work. If the client keeps requesting GPU work with every scheduler contact, it will probably never get CPU from the locality scheduler (it will get CPU work from the "array scheduler", though, i.e. FGRP5).
If I understand correctly then if I only request CPU GW jobs (so "Gravitational Wave search O2 Multi-Directional GPU" is not selected) and/or the "Use XXX GPU" options are not selected then it shouldn't be requesting any GPU work and my PC should get CPU work. This isn't happening, not for GW jobs anyway.
If you haven't already, try to enable "Run test applications", I managed to get CPU GW work by doing that.
Yes, that worked. Thanks.
It's not really ideal and this seems to be a reoccurring problem. On this forum I've repeatedly read comments from people not getting work for their selected applications. Perhaps the event log in BOINC needs to have entries stating the first reason why no work was delivered for the selected applications. The scheduler will filter out jobs for a number of reasons but if it can find jobs by dropping certain criteria, then it could report that. In this particular case a message stating that no regular jobs are available but test jobs are would have been helpful.
If you haven't already, try to enable "Run test applications", I managed to get CPU GW work by doing that.
Yes, that worked. Thanks.
It's not really ideal and this seems to be a reoccurring problem. On this forum I've repeatedly read comments from people not getting work for their selected applications. Perhaps the event log in BOINC needs to have entries stating the first reason why no work was delivered for the selected applications. The scheduler will filter out jobs for a number of reasons but if it can find jobs by dropping certain criteria, then it could report that. In this particular case a message stating that no regular jobs are available but test jobs are would have been helpful.
It definitely could've been clearer; but the needed information was in the scheduler log. From one of my boxes before turning on beta:
The remaining data couldn't be run on GWold (first 3 lines); but GWnew wasn't available because I had beta applications turned off. (Previously the only way to opt out of GW-GPU testing while doing GW-CPU apps and Fermi-GPU.)
2019-12-12 11:44:07.1655 [PID=17184] [version] Checking plan class 'GWold'
2019-12-12 11:44:07.1688 [PID=17184] [version] reading plan classes from file '/BOINC/projects/EinsteinAtHome/plan_class_spec.xml'
2019-12-12 11:44:07.1688 [PID=17184] [version] WU#424750889 too new
2019-12-12 11:44:07.1688 [PID=17184] [version] Checking plan class 'GWnew'
2019-12-12 11:44:07.1688 [PID=17184] [version] plan class ok
2019-12-12 11:44:07.1688 [PID=17184] [version] beta test app versions not allowed in project prefs.
2019-12-12 11:44:07.1689 [PID=17184] [version] no app version available: APP#53 (einstein_O2MD1) PLATFORM#9 (windows_x86_64) min_version 0
2019-12-12 11:44:07.1689 [PID=17184] [version] no app version available: APP#53 (einstein_O2MD1) PLATFORM#2 (windows_intelx86) min_version 0
After a disappointing result trying "Gravitational Wave search O2 Multi-Directional GPU" about two months ago (they all timed out and I was told that my GPU was too slow), I decided to give it another go since they are no longer beta status. I watched one of them for about 30 minutes and in BOINC its progress made its way up to about 95% and the remaining time reduced down to about 1 minute 30 seconds. After making steady and consistent progress, the progress indicator suddenly jumped back down to less than 1% and the remaining time was shown in multiple days.
My AMD Radeon HD 7700 is not the newest and most powerful thing around but this looks like a bug to me.
I watched one of them for about 30 minutes and in BOINC its progress made its way up to about 95% and the remaining time reduced down to about 1 minute 30 seconds. After making steady and consistent progress, the progress indicator suddenly jumped back down to less than 1% and the remaining time was shown in multiple days.
As the task runs really slow and thus doesn't report any progress Boinc will simulate progress, that's what you're seeing. This simulation will got towards but never reach 100%. Then when the task finally reaches a point where it will report some progress Boinc stops the simulation and switches to show actual progress as reported by the task.
As the task runs really slow and thus doesn't report any progress Boinc will simulate progress, that's what you're seeing. This simulation will got towards but never reach 100%. Then when the task finally reaches a point where it will report some progress Boinc stops the simulation and switches to show actual progress as reported by the task.
Well that's just absurd. Who's responsible for a silly idea like that? The progress information is just totally bogus and therefore worthless.
There is still "O2MD1" work
)
There is still "O2MD1" work for the CPUs. However currently the "locality scheduler" only makes one pass per work request (GPU or CPU). if the client requests work for the GPU, it will (try to) send GPU work. If the client keeps requesting GPU work with every scheduler contact, it will probably never get CPU from the locality scheduler (it will get CPU work from the "array scheduler", though, i.e. FGRP5).
BM
If I understand correctly
)
If I understand correctly then if I only request CPU GW jobs (so "Gravitational Wave search O2 Multi-Directional GPU" is not selected) and/or the "Use XXX GPU" options are not selected then it shouldn't be requesting any GPU work and my PC should get CPU work. This isn't happening, not for GW jobs anyway.
If you haven't already, try
)
If you haven't already, try to enable "Run test applications", I managed to get CPU GW work by doing that.
Holmis wrote:If you haven't
)
Yes, that worked. Thanks.
It's not really ideal and this seems to be a reoccurring problem. On this forum I've repeatedly read comments from people not getting work for their selected applications. Perhaps the event log in BOINC needs to have entries stating the first reason why no work was delivered for the selected applications. The scheduler will filter out jobs for a number of reasons but if it can find jobs by dropping certain criteria, then it could report that. In this particular case a message stating that no regular jobs are available but test jobs are would have been helpful.
Mr Anderson wrote:Holmis
)
It definitely could've been clearer; but the needed information was in the scheduler log. From one of my boxes before turning on beta:
The remaining data couldn't be run on GWold (first 3 lines); but GWnew wasn't available because I had beta applications turned off. (Previously the only way to opt out of GW-GPU testing while doing GW-CPU apps and Fermi-GPU.)
This is weird, there is a
)
This is weird, there is a "Beta" version (2.05) and a version that's non-Beta (2.00). You should get work, but with teh 2.00 App version.
Anyway, I just promoted the 2.05 version out of Beta test, you should now get CPU work in any case.
BM
After a disappointing result
)
After a disappointing result trying "Gravitational Wave search O2 Multi-Directional GPU" about two months ago (they all timed out and I was told that my GPU was too slow), I decided to give it another go since they are no longer beta status. I watched one of them for about 30 minutes and in BOINC its progress made its way up to about 95% and the remaining time reduced down to about 1 minute 30 seconds. After making steady and consistent progress, the progress indicator suddenly jumped back down to less than 1% and the remaining time was shown in multiple days.
My AMD Radeon HD 7700 is not the newest and most powerful thing around but this looks like a bug to me.
Mr Anderson wrote:I watched
)
As the task runs really slow and thus doesn't report any progress Boinc will simulate progress, that's what you're seeing. This simulation will got towards but never reach 100%. Then when the task finally reaches a point where it will report some progress Boinc stops the simulation and switches to show actual progress as reported by the task.
Holmis wrote:As the task runs
)
Well that's just absurd. Who's responsible for a silly idea like that? The progress information is just totally bogus and therefore worthless.
... totally bogus and
)
... totally bogus and therefore worthless.
YES, for you!
Just crunch and relax!
Have a nice day.