Switched to Intel GPU, and I've still got

30/11/2018 13:45:36 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 530 (driver version 23.20.16.4973, device version OpenCL 2.1 NEO, 3231MB, 3231MB available, 202 GFLOPS peak)

(and Windows Update says there's nothing more to update)

I know that one works, so I'll manually install uwd_win64_25.20.100.6444 and see where that takes us.

Bu**er. Intel says it's an OEM driver, and won't update it. I've worked round that in the past, with the .zip format download, but...

Manual installation format (.zip) is intended for developers and IT professionals (not provided for this release).

And the OEM doesn't have the UWD driver available yet. I think I'm stuck for the time being - I don't have Windows 10 on a non-OEM platform.

I can confirm that. I switched off the Intel client on the Windows machine 2 days ago and the CPU tasks are running more than twice as fast. Thank you.
greetings Klaus

Bu**er. Intel says it's an OEM driver, and won't update it. I've worked round that in the past, with the .zip format download, but...

Manual installation format (.zip) is intended for developers and IT professionals (not provided for this release).

And the OEM doesn't have the UWD driver available yet. I think I'm stuck for the time being - I don't have Windows 10 on a non-OEM platform.

If I remember correctly, I had the same problem when I installed ASrock's video driver when I initially built this machine. I uninstalled the driver and removed all instances from the registry before recyclng the machine and letting M$S install its' default driver. After that I was able to install all of Intel's video drivers including the new UWD, after setting the M$S hardware driver installations to no. I don't know if would help, but you might want to give it a try if you'r so inclined. BTW, my OS is from a system builder DVD.

---

I don't buy computers, I build them!!

Thanks for the reminder. Yes, that works - I'm now running with

01/12/2018 16:48:01 |  | OpenCL: Intel GPU 0: Intel(R) HD Graphics 530 (driver version 25.20.100.6444, device version OpenCL 2.1 NEO, 3231MB, 3231MB available, 202 GFLOPS peak)

Results will appear for host 8508571 at a time yet to be determined - depends whether TBar's observation remains true for this machine, this configuration, this driver.

BTW, this is how fast a recent i5 will run using a decent CPU App with the iGPU disabled, Run time : 40 min 39 sec
My particular i5-6600 will run a single BLC cpu task in about 29 minutes. Much better than the HOURS that are associated with CPUs also running the iGPU App.

Yes, my results are starting to show about a doubling (but still under 2 hours) - make sure you discount the oveflows. I'm now running what will be the third and final SETI iGPU task: after that, I'll switch to using the Einstein iGPU app, and see what effect that has on SETI CPU runtime. Then I'll pop the 1050Ti back in, and return to production work, while we wait for wingmates to supply the validation test results.

Even though I'm glad you guys are showing results , remember you pulled the driver directly from Intel. I don't know if M$S will strip OpenCL from the driver as they have been doing. Will they or won't they, THAT IS THE BIG QUESTION. M$S claims that UWD is supposed to be universal, but seeing how the 1809 update is still going south, I'm very skeptical. Something someone with better connections with Intel & M$S than me can/should explore if possible.

---

I don't buy computers, I build them!!

I've reached the end of my testing for this thread. Both SETI and Einstein tasks have run normally using the new UWD Intel HD graphics Driver Version 25.20.100.6444 on Windows 10 1809.

So far, no wingmates have reported at either project, so I can't yet comment on accuracy - but I'll keep my eyes open for validations, and report here if any problems appear.

The only oddity seems to be that the Einstein iGPU app now reports using as many CPU seconds as runtime seconds: the same app running under Windows 7 and an older driver only reports about 20 seconds CPU time in a 630 second run. I don't know whether that's a Windows 10 change, or a UWD change.

Yes, that's the remaining question. My observations are that they've been putting back CUDA (for NVidia) and OpenCL (for Intel only) since about this time last year. We'll have to wait and see if they learned their lesson for all time.