Message boards :
Number crunching :
Intel GPU App ready?
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
But it repeated again: You swapped out 43 completed CPU and NVidia tasks, and got exactly the same mixture in return. Did you see my suggestion of temporarily disabling NV in your preferences, so that next time you report NV, you get Intel to top up your GPU quota? And your cache is still more than you need, to an absurd degree - you're still asking for six days. Even with 100 NVidia tasks cached, your client still wanted another 5 days of work for them to reach your target cache. You have two cards, so your cache request is still 2.5 days too high to fill both device classes. Cut it down to 2 days or less - at least while testing. |
Ulrich Metzner Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13 |
Here is my part of the app_info.xml, which is working as expected. Maybe this can help: <app_version> <app_name>setiathome_v7</app_name> <version_num>703</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>intel_opencl_sah</plan_class> <cmdline></cmdline> <coproc> <type>intel_gpu</type> <count>1</count> </coproc> <file_ref> <file_name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r2061.cl</file_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v7</app_name> <version_num>703</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_intel_sah</plan_class> <cmdline></cmdline> <coproc> <type>intel_gpu</type> <count>1</count> </coproc> <file_ref> <file_name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r2061.cl</file_name> </file_ref> </app_version> Please keep in mind, i'm using the name convention from seti BETA project, that's why the executable has another name. This was made long before intel was on seti main project. I also see different plan classes? Hope, this helps, Raistmer, i very much appreciated your work! Aloha, Uli |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Thanks, finally I got 2 tasks under opencl_intel_gpu_sah. So it was all GPU-wide limit indeed just as Richard said. Able to test next app version now. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Rick A. Sponholz Send message Joined: 13 Jun 99 Posts: 43 Credit: 23,179,807 RAC: 0 |
Hi there, I have the same situation of using lunatic's optimized app for seti. Does anyone know how/what to add to the app_info file to get seti to run on my intel gpu's? Thanks in advance, Rick |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
Hope, this helps, Raistmer, i very much appreciated your work! Having 0 GPU tasks and adding Intel GPU app to this host: 02-Feb-2014 14:29:03 [SETI@home] Sending scheduler request: To fetch work. Scheduler seemed very happy to see me. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Does anyone know how/what to add to the app_info file to get seti to run on my intel gpu's? Ah, that's the other thing I was going to do this weekend, wasn't it? The plan was to wait for AP tasks to be split, and then do both apps together. Well, AP has been split, and - nada. Checking the front page, the announcement says "We've released SETI@home 7.03 for Intel GPUs that support OpenCL 1.2". Yup, that's MB only - no AP release. I take it as axiomatic that Eric knows what he's doing, so there will be a reason why not: possibly validation rate problems in Beta, or simply too many volunteers chasing too few tasks. Whatever, I'm not going to jump the gun. But this app_info for MB is what you need. Assuming that you run a 64-bit version of Windows, this will preserve cached intel_gpu tasks issued as stock. (For 32-bit OSs, remove the <platform> line - but I'm assuming few volunteers will run 32-bit on such new processors) <app_info> <app> <name>setiathome_v7</name> </app> <file_info> <name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</name> <executable/> </file_info> <file_info> <name>MultiBeam_Kernels_r2061_windows_intel_gpu.cl</name> <executable/> </file_info> <file_info> <name>libfftw3f-3.dll</name> <executable/> </file_info> <file_info> <name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</name> </file_info> <app_version> <app_name>setiathome_v7</app_name> <version_num>703</version_num> <platform>windows_intelx86</platform> <coproc> <type>intel_gpu</type> <count>1</count> </coproc> <plan_class>opencl_intel_gpu_sah</plan_class> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.04</max_ncpus> <file_ref> <file_name>setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r2061_windows_intel_gpu.cl</file_name> <open_name>MultiBeam_Kernels_r2061.cl</open_name> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline-7.03-opencl_intel_gpu_sah.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> </app_info> You must also - as always - supply the necessary files manually. Here are the download links: http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_7.03_windows_intelx86__opencl_intel_gpu_sah.exe (931 KB) http://boinc2.ssl.berkeley.edu/sah/download_fanout/libfftw3f-3.dll (2,235 KB) http://boinc2.ssl.berkeley.edu/sah/download_fanout/MultiBeam_Kernels_r2061_windows_intel_gpu.cl (114 KB) http://boinc2.ssl.berkeley.edu/sah/download_fanout/mb_cmdline-7.03-opencl_intel_gpu_sah.txt (0 bytes) The last one is an empty file - a placeholder for future options. Browsers won't allow a manual download, so just create an empty text file called "mb_cmdline-7.03-opencl_intel_gpu_sah.txt". We'll get somebody at Lunatics to put together notes on what cmd options are available for this specific build (the online readme file is wrong), but the app runs fine with the file empty. Important notes 1) Check that you have a compatible Intel chip before wasting any time. You need one of 3rd Generation Intel® Core™ Processors with: Intel® HD Graphics 4000/2500 4th Generation Intel® Core™ Processors with: Intel® HD Graphics 4200/4400/4600/5000 Intel® IrisTM Graphics 5100 Intel® IrisTM Pro graphics 5200 2) Use an Intel GPU driver which supports OpenCL 1.2: the recommended package (assuming a 64-bit OS, as before) is Win64_153117 - available in both .EXE and .ZIP form from the Intel Download Center. This driver (9.18.10.3257) is compatible with both SETI and Einstein applications: there is a 32-bit version available too, if you persevere with the Intel search tools. 3) Connect the display output from your Intel GPU to a suitable load - a spare monitor port or dummy plug. 4) Use a current version of BOINC for correct Intel GPU detection - v7.2.33 (recommended) or v7.2.39 (testing) are best. Check http://boinc.berkeley.edu/download_all.php. 5) If you have been Beta testing an earlier version of the Intel OpenCL application under app_info, check that you have been using the same <plan_class>. If you need to transition, place this <app_version> higher in the combined app_info than your existing entries, and verify that newly fetched work is marked as 'opencl_intel_gpu_sah'. This will help you achieve painless upgrades with future releases of the Lunatics installer. |
Rick A. Sponholz Send message Joined: 13 Jun 99 Posts: 43 Credit: 23,179,807 RAC: 0 |
Richard, After several days of trying to merge the app_info file you posted with the app_info file generated by Lunatics' installer, I still need more help. How do I merge these two files, so seti will also work on the intel gpu? seti beta is working fine on both of my intel gpu's. BTW, the machines also have two GTX690's running other projects and seti on them. Thanks again, Rick |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Richard, The process is very much as I described to Bil in message 1471242: You will need to 'splice' the two app_info files together - link them together, one after the other, but take out the I'd suggest that you copy the Lunatics generated file to a temporary folder so you can work on it. Open the file for editing with whatever simple text editor you usually use. The Windows-supplied 'Notepad' is ideal. Then, paste the Intel GPU file at the very end, after everything else. Finally, take out the two lines above to hide the join, and save the combined file. That's really all you need to do. Check it all by eye, put it back into the project directory (replacing the existing file), and re-start BOINC. |
Ulrich Metzner Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13 |
(...) ...and ensure, it's saved with the name "app_info.xml" and NOT "app_info.xml.txt", as often accidentally done by users having file extensions hidden in Windows. ;) Aloha, Uli |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.