Tomorrow I'll try with the system fully loaded on all 8 threads and the GTX660Ti.
So I just did a short test with the computer otherwise fully loaded with 8 Einstein tasks on the CPU and 2 BRP5 tasks on the GPU, the result was as I suspected from experience with other OpenCL apps. The GPU load reported by GPU-Z dropped to ~20-25% and as soon as I suspended tasks in Boinc to free up one thread the GPU load returned to about 80%, so the conclusion is that this app needs one thread free to run at optimal speed.
From comments on other projects' message boards this seems to be a driver issue when one runs OpenCL apps both on Intel and Nvidia GPUs.
Finally I got the BRP app running even under BOINC control on my PC. Because the server software doesn't yet support Intel GPUs (and it's not trivial to add the support in our customized server software), it is a combination of app_info.xml and cc_config.xml file hack.
I used this cc_config.xml file (goes into the BOINC data directory):
Quote:
1
1
intel_gpu
1
0
Where should be set to the device number of your Intel HD GPU (see above) (here 0 in this example).
The app_info.xml file (goes into the projects\albert.phys.uwm.edu sub directory):
Quote:
einsteinbinary_BRP4U
Binary Radio Pulsar Search nr 4 single task
This assumes you have renamed the downloaded executable to einsteinbinary_BRP4U_1.35_windows_x86_64__opencl-intel_gpu.exe . This will process the unbundled BRP4U workunits to allow speedy tests.
The tasks should automatically reserve a full CPU core.
On my PC, I now get close to 100% GPU usage this way, according to GPU-Z. So running many of these units in parallel on my HD 2500 GPU would not help.
I used the currently recommended BOINC client version for this.
Nice to see you got it running under Boinc, will definitely make it easier to test and validate!
I've just completed the first BRP4U task and it took 18m30s on the HD 4000, the average GPU load according to GPU-Z was 76% and it varies between 75-85%.
As a note to other testers the log flag in cc_config.xml is not needed for this to work, what it does is tell you which coproc Boinc assigns a task to and then at regular intervals it confirms the assignment.
As I was composing this the second task completed (18m21s) and validated against the Neon-app! =)
Oh and by the way did my first standalone test "validate"?
I have seen that the intel open-cl app is for linux only; are there plans to port that to windows too? Otherwise I will try to install a dual boot system over the weekend.
No, the app is for Windows, I'm running it on Win7 x64.
Download the app from the post about standalone test but then follow the instructions about using a app_info.xml and cc_config.xml to get it running. Don't forget to rename the .exe or make the appropriate changes to the app_info.
That entry is caused by a deprecated app, it was never used in the project.
The only OpenCL driver for Linux that Intel offers is supporting the CPU cores itself (so for multi-threading CPU programs), and the Xeon Phi accelerator card, not for the build-in Intel HD GPUs :-(
Hi! Thanks very much, see
Hi!
Thanks very much, see your PM box for an address to send the result files to.
I think for an integrated GPU the runtime isn't shabby at all.
Thanks again!
HB
RE: Tomorrow I'll try with
So I just did a short test with the computer otherwise fully loaded with 8 Einstein tasks on the CPU and 2 BRP5 tasks on the GPU, the result was as I suspected from experience with other OpenCL apps. The GPU load reported by GPU-Z dropped to ~20-25% and as soon as I suspended tasks in Boinc to free up one thread the GPU load returned to about 80%, so the conclusion is that this app needs one thread free to run at optimal speed.
From comments on other projects' message boards this seems to be a driver issue when one runs OpenCL apps both on Intel and Nvidia GPUs.
Hi! Finally I got the BRP
Hi!
Finally I got the BRP app running even under BOINC control on my PC. Because the server software doesn't yet support Intel GPUs (and it's not trivial to add the support in our customized server software), it is a combination of app_info.xml and cc_config.xml file hack.
I used this cc_config.xml file (goes into the BOINC data directory):
Where should be set to the device number of your Intel HD GPU (see above) (here 0 in this example).
The app_info.xml file (goes into the projects\albert.phys.uwm.edu sub directory):
This assumes you have renamed the downloaded executable to einsteinbinary_BRP4U_1.35_windows_x86_64__opencl-intel_gpu.exe . This will process the unbundled BRP4U workunits to allow speedy tests.
The tasks should automatically reserve a full CPU core.
On my PC, I now get close to 100% GPU usage this way, according to GPU-Z. So running many of these units in parallel on my HD 2500 GPU would not help.
I used the currently recommended BOINC client version for this.
Cheers
HB
Nice to see you got it
Nice to see you got it running under Boinc, will definitely make it easier to test and validate!
I've just completed the first BRP4U task and it took 18m30s on the HD 4000, the average GPU load according to GPU-Z was 76% and it varies between 75-85%.
Link to BRP4U tasks on host #2267
As a note to other testers the log flag in cc_config.xml is not needed for this to work, what it does is tell you which coproc Boinc assigns a task to and then at regular intervals it confirms the assignment.
As I was composing this the second task completed (18m21s) and validated against the Neon-app! =)
Oh and by the way did my first standalone test "validate"?
RE: Oh and by the way did
Oh yes, just checked it by diff and eyeball and spotted only insignificant differences.
Cheers
HB
I have seen that the intel
I have seen that the intel open-cl app is for linux only; are there plans to port that to windows too? Otherwise I will try to install a dual boot system over the weekend.
No, the app is for Windows,
No, the app is for Windows, I'm running it on Win7 x64.
Download the app from the post about standalone test but then follow the instructions about using a app_info.xml and cc_config.xml to get it running. Don't forget to rename the .exe or make the appropriate changes to the app_info.
AFAIK Intel doesn't even
AFAIK Intel doesn't even provide an OpenCL-capable driver for Linux.
BM
BM
So this entry on the
So this entry on the application page is a fake?
Linux running on an AMD x86_64 or Intel EM64T CPU 1.34 (opencl-intel_gpu) 20 Mar 2013 | 10:19:43 UTC
Anyway, I get the pc over the weekend and will try that.
Thx for the reply!
That entry is caused by a
That entry is caused by a deprecated app, it was never used in the project.
The only OpenCL driver for Linux that Intel offers is supporting the CPU cores itself (so for multi-threading CPU programs), and the Xeon Phi accelerator card, not for the build-in Intel HD GPUs :-(
Cheers
HB