Message boards :
Number crunching :
New AstroPulse for GPU ( ATi & NV) released (r1316)
Message board moderation
Author | Message |
---|---|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
New AstroPulse binaries are available here: http://lunatics.kwsn.net/12-gpu-crunching/ap6-for-nv-ati-gpus-r1316-released.msg49053.html#msg49053 Please, report noticed issues in this thread. |
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
New AstroPulse binaries are available here: http://lunatics.kwsn.net/12-gpu-crunching/ap6-for-nv-ati-gpus-r1316-released.msg49053.html#msg49053 Got it installed, have some questions: 1) On the Lunatics site, it says: On hosts with BOINC supporting OpenCL app will use device supplied by BOINC. With older BOINC versions own enumeration ability will be used. Not sure what this means - what do I need to do for 6.12.34? 2. Modified the suggested app_info.xml from ATI to NV as follows: <app> <name>astropulse_v6</name> </app> <file_info> <name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe<app> <executable/> </file_info> <app_version> <app_name>astropulse_v6</app_name> <version_num>604</version_num> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda</plan_class> <cmdline></cmdline> <coproc> <type>cuda</type> <count>.5</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_NV_r1316.exe</file_name> <main_program/> </file_ref> </app_version> Will this work? I omitted the flops entry since I'm now running without them and would have to guess at a value anyway. Will add back if need arises. Waiting for work, hope they mount some new files soon. Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. |
rob smith Send message Joined: 7 Mar 03 Posts: 22204 Credit: 416,307,556 RAC: 380 |
I notice that the current offerings are all win-x86, are there plans for win-64 versions? Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
Second big change - there is ap_cmdline.txt file that can be used to add command line parameters to app. Which one will be used if they contradict? (e.g. * in app_info.xml <cmdline>-unroll 3 -ffa_block 2048 -ffa_block_fetch 1024</cmdline> * in ap_cmdline.txt -unroll 6 -ffa_block 2048 -ffa_block_fetch 1024 ) Will this erase AP ATI 601 tasks on-board?: <version_num>604</version_num> I think I need second 'copy' section with: <version_num>601</version_num> P.S. It will be good to supply APATI.aistub (two of them - for 32 and 64 bit) in the .7z  - ALF - "Find out what you don't do well ..... then don't do it!" :)  |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Here is an example for ATI cards. Just use ap_cmdline.txt instead of comand line in appinfo. So you can edit params without restarting Boinc. Type has to be uppercase. ATI or CUDA <app> <name>astropulse_v6</name> </app> <file_info> <name>AP6_win_x86_SSE2_OpenCL_ATI_r1316.exe</name> <executable/> </file_info> <file_info> <name>ap_cmdline.txt</name> </file_info> <app_version> <app_name>astropulse_v6</app_name> <version_num>601</version_num> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>ati13ati</plan_class> <coproc> <type>ATI</type> <count>0.5</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1316.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>ap_cmdline.txt</file_name> </file_ref> </app_version> @ Fred E. You dont need to do anything for 6.12 version. Just check you appinfo with mine. Mike With each crime and every kindness we birth our future. |
Horacio Send message Joined: 14 Jan 00 Posts: 536 Credit: 75,967,266 RAC: 0 |
Question: Is this new release still affected by the high cpu usage on newer drivers? |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
I notice that the current offerings are all win-x86, are there plans for win-64 versions? It's GPU build. I'm not expect big improvement from x64 one. And this binary perfectly can work under x64 Windows OS |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Question: Yes, cause nothing was done in drivers still. They still use busy-wait loop. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Second big change - there is ap_cmdline.txt file that can be used to add command line parameters to app. 1) If I remember correct text file processed after command line so params will be overwritten. It's easy to check cause app reports if default param replaced. 2) yes, better to make copy or just create this new section leaving old one untouched. 3) I think aistub will be supplied in next installer release. It's standalone app release. |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
If cmdline.txt is not mentioned in appinfo it will be untouched on most hosts. With each crime and every kindness we birth our future. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
[quote]New AstroPulse binaries are available here: Not sure what this means - what do I need to do for 6.12.34? Nothing. It was just some info about new app abilities and possible diffrence in experience under BOINC 7 and pre-7. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Regarding what to mention in app_info file: for stock users upgrading to this release it would be better to include libfftw3f-3.dll in app_info. That's because stock version could mention it already. If you have this file in project dir then you need to mention it to save it from deletion. It's BOINC's paranoid "kill all I know" approach - quite useless cause nothing prevents to accumulate not known to BOINC trash in that folders. In general, upgrading with big cache of tasks is not recommended cause chances to lost all accumulated work and work in progress quite big (the same "wipe all" approach in action). I would recommend to finish current GPU AP work, set to "no new task", do update then enable work fetch. In this case errors in app_info will cause minimal damage. |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
Question: Since there's been many driver updates since the last working version, I've been wondering if that driver bug is a bug or just the way the drivers work now? |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Question: It is a bug. It was the same with ATI drivers. AMD fixed it. With each crime and every kindness we birth our future. |
JohnDK Send message Joined: 28 May 00 Posts: 1222 Credit: 451,243,443 RAC: 1,127 |
Question: Thanks, who will kick NV in the butt then? ;) |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Question: I think it more depends on their strategy in particular. With each crime and every kindness we birth our future. |
Fred J. Verster Send message Joined: 21 Apr 04 Posts: 3252 Credit: 31,903,643 RAC: 0 |
Question: I'm gonna try this on 2 ATI 5870 GPUs, can I still use command-line parameters like unroll 15, ffa_block 10240 & fetch 5120, 1 per device) ? On AstroPulse work? Or is it MB only? Bêta work? |
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
Completed my first Task. It ran very fast - was on track for about an hour running with 2 MB 6.10 tasks at the same time, but exited early at the 35 minute mark with "Found 30 single pulses and 30 repeating pulses, exiting." Was only split tonight so it won't validate for a long time. CPU use was high - about 21% with driver 301.42 (I'm not currently reserving a CPU core for the GPU). There are several warnings in the StdErr you might want to review. One seems to be about the BOINC version I'm using, and I'm not concerned after your earlier comments. The other has to do with inability to open a file: "INFO: can't open binary kernel file: C:\BoincData/projects/setiathome.berkeley.edu\AstroPulse_Kernels_r1316.cl_GeForceGTX670.bin_V6, continue with recompile..." and another similar message labeled "Warning". Maybe because it's the first time? Or my non=standard data directory location? Guess my app_info.xml section is okay. Anyone looking at that earlier in this thread needs to make the fix that Mike pointed out - CUDA needs to be upper case on the Type line. Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Question: It can be called in different ways, but the facts are: 1) there is 2 fundamental ways for CPU to communicate with hardware: to read from port or mapped memory and to process hardware interrupt. First one result in busy wait loop. 2) Earlier drivers work on the same hardware with the same software and low CPU usage method. Current ones use lot of CPU. So, apparently, method for synching was changed. 3) Both methods are possible technically, even with new drivers, CUDA runtime demonstrate this. But NV did not expose ability to switch over driver modes into OpenCL runtime. Call it but or call it feature - no matter. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Yes, such output should appear at first running of new versionBut if one sees it always it would mean that kernels binary cache was not saved. First time app compiles OpenCL kernels from CL file (and oclFFT kernels) into binary representation and saves those binary representations into project directory. In case of NV those "binary representations" are mostly text one actually - PTX assembly saved so one who interesting can look and see what assembly instructions were generated from original OpenCL code. |
©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.