1)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1373622)
Posted 30 May 2013 by Martin Post: Thanks for your quick response William! |
2)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1373607)
Posted 30 May 2013 by Martin Post: Personnaly I'd wait till Monday or so and use the installer. Will Lunatics installer also be available for win OS? It look like it's only for Linux.. Maybe I am wrong? |
3)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1373575)
Posted 30 May 2013 by Martin Post: Hello again:-) Now it runs at 100% when i'm using enhanced 6.10 (ati13ati) Before I was running astropuls_v6.. Anyway I am happy right now :-) |
4)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1373560)
Posted 30 May 2013 by Martin Post: Personnaly I'd wait till Monday or so and use the installer. What will happen then? And where can I find the installer on monday? |
5)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1373556)
Posted 30 May 2013 by Martin Post: Thanks for the link spitfire_mk_2! But I'm still not happy with my GPU load... The load is the same when I run one WU or three! (30-65%) What parameter can I change that with? And I am using 6 of 8 cores on the cpu. Here is my app_info.xml using Lunatics_Win64. <app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>AK_v8b2_win_SSE3_AMD.exe</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> <platform>windows_intelx86</platform> <file_ref> <file_name>AK_v8b2_win_SSE3_AMD.exe</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> <platform>windows_x86_64</platform> <file_ref> <file_name>AK_v8b2_win_SSE3_AMD.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v6</name> </app> <file_info> <name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</name> <executable/> </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> <platform>windows_intelx86</platform> <plan_class>ati13ati</plan_class> <cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name> <main_program/> </file_ref> </app_version> <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> <platform>windows_x86_64</platform> <plan_class>ati13ati</plan_class> <cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v505</name> </app> <app_version> <app_name>astropulse_v505</app_name> <version_num>506</version_num> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <platform>windows_intelx86</platform> <plan_class>ati13ati</plan_class> <cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>astropulse_v505</app_name> <version_num>505</version_num> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <platform>windows_intelx86</platform> <plan_class>ati13ati</plan_class> <cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>astropulse_v505</app_name> <version_num>506</version_num> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <platform>windows_x86_64</platform> <plan_class>ati13ati</plan_class> <cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>astropulse_v505</app_name> <version_num>505</version_num> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <platform>windows_x86_64</platform> <plan_class>ati13ati</plan_class> <cmdline>-instances_per_device 1 -unroll 4 -ffa_block 2048 -ffa_block_fetch 1024 -sbs 128 -v505</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r555.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>MB6_win_x86_SSE3_OpenCL_ATi_r390.exe</name> <executable/> </file_info> <file_info> <name>MultiBeam_Kernels_r390.cl</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>610</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>0.05</max_ncpus> <plan_class>ati13ati</plan_class> <cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>MB6_win_x86_SSE3_OpenCL_ATi_r390.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r390.cl</file_name> <copy_file/> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>610</version_num> <platform>windows_x86_64</platform> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>0.05</max_ncpus> <plan_class>ati13ati</plan_class> <cmdline>-period_iterations_num 20 -instances_per_device 1</cmdline> <coproc> <type>ATI</type> <count>0.33</count> </coproc> <file_ref> <file_name>MB6_win_x86_SSE3_OpenCL_ATi_r390.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r390.cl</file_name> <copy_file/> </file_ref> </app_version> </app_info> |
6)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1373123)
Posted 29 May 2013 by Martin Post: Thanks for your reply! But what I really want to know is how my app_info.xml should look like on the stock application? Just to use more the one WU on each GPU, and still running WU's on the CPU. I have been using app_info.xml one time before when I was running Milkyway on my GPU only, and it worked great! It's looks like this: <app_info> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>102</version_num> <flops>1.0e11</flops> <avg_ncpus>0.05</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>ati14ati</plan_class> <coproc> <type>ATI</type> <count>0.5</count> </coproc> <cmdline></cmdline> <file_ref> <file_name>milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe</file_name> <main_program/> </file_ref> </app_version> </app_info> So if someone have an working app_info.xml for both CPU/GPU please share! Thanks |
7)
Message boards :
Number crunching :
AMD GPU & CPU together working on SETI
(Message 1371525)
Posted 24 May 2013 by Martin Post: Hello everyone! My question is how can I run my dual AMD 6950 with TWO work units on each card, plus I also want to run at maximum on my CPU. Any good and easy suggestion would be much appreciated! ( My computer http://setiathome.berkeley.edu/hosts_user.php?userid=9810505 ) |
©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.