Catalyst 13.4


log in

Advanced search

Message boards : Number crunching : Catalyst 13.4

Author Message
Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1366719 - Posted: 11 May 2013, 11:03:46 UTC

Is it just me - I'm not getting any GPU Applications after upgrading to Catalyst 13.4 - Well, I did get some Apps for a while but they took so long to compute. And looking at various 'resource' monitors I found the CPU was working very hard and the GPU was processing intermittently and not much when it did.

So before revert to 12.8... Are there any GPU Apps available at the moment?
I mean - Or has the project decided my new driver augmented GPUs are not worth sending out for?

Much obliged.
____________

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 23378
Credit: 31,813,675
RAC: 24,403
Germany
Message 1366721 - Posted: 11 May 2013, 11:07:31 UTC
Last modified: 11 May 2013, 11:08:24 UTC

You are running stock application so you can only process astropulse units.
But there is no work available atm.

If you are able to create/edit appinfo.xml you can run optimized apps as well.

See here.

http://setiathome.berkeley.edu/forum_thread.php?id=53611
____________

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1366728 - Posted: 11 May 2013, 11:40:14 UTC

Ah, that's interesting, Mike.

So. Is it safe to install these new Apps while I have CPU tasks in progress?

11/05/2013 07:20:35 | SETI@home | Starting task 09oc11ad.31898.7192.3.11.130.vlar_0 using setiathome_enhanced version 603 in slot 1
11/05/2013 07:38:14 | SETI@home | Starting task 09oc11ac.29292.6370.5.11.50.vlar_1 using setiathome_enhanced version 603 in slot 0

I have nothing on the GPUs so that App is going on immediately! Or not...?

Thanks
____________

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 23378
Credit: 31,813,675
RAC: 24,403
Germany
Message 1366734 - Posted: 11 May 2013, 12:26:30 UTC

Its not that easy.
You need a appinfo section for the CPU app also.
Otherwise you`ll loose all your work.

____________

chromespringer
Avatar
Send message
Joined: 3 Dec 05
Posts: 269
Credit: 18,857,177
RAC: 34,166
United States
Message 1366786 - Posted: 11 May 2013, 16:26:39 UTC
Last modified: 11 May 2013, 16:48:06 UTC

upgraded from cat12.8 to cat13.4 this morning .. boinc version 7.0.64 running lunatics .40 on win7 64-bit with no issues as yet on mach 0084
____________

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1366845 - Posted: 11 May 2013, 18:54:37 UTC - in response to Message 1366786.
Last modified: 11 May 2013, 19:02:27 UTC

That's encouaging, chromespringer.
My problem is - ignorance. I've not used optimised apps before. Reading about how to set it up is like chasing your own tail - the information is often oudated and strung out thinly over many domains.
I would be happier to test a few configs if I had the confidence: I could loose the WUs already here when it (the config) is done incorrectly.
One of the basic pieces of info I'm in conflict about is the name of the config file to create, and where. Clearly, it's up to me to find out what to put in it. But help in any of these areas would be gratefully received.
Thanks -

Win7-64bit, ATI HD6950 x2, BOINC 7.0.64
____________

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1366852 - Posted: 11 May 2013, 19:32:57 UTC - in response to Message 1366845.
Last modified: 11 May 2013, 20:10:02 UTC

Elaboration: (for Windows 7)

app_info.xml - I see that lives in

C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\

And so, if I'm using the two Lunatics optimised apps -

AP6_win_x86_SSE2_OpenCL_ATI_r1812
MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817

- is it wise to have app_info.xml recognise the 'stock CPU' apps? I presume, to continue processing the WUs I already have. Or does the Optimised MultiBeam app process these WUs? (cool)

Thanks -
____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4048
Credit: 32,693,237
RAC: 546
United Kingdom
Message 1366872 - Posted: 11 May 2013, 20:40:03 UTC - in response to Message 1366852.

There's no problem with running the Stock CPU app via anonymous platform, it just won't be as fast as one of the (presently unavailable) MB Optimised apps,
here is a CPU only app_info.xml using the Stock 6.03 app, it should work with no problem:

<app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>setiathome_6.03_windows_intelx86.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-1-1a_upx.dll</name> <executable/> </file_info> <file_info> <name>setigraphics_6.03_windows_intelx86.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>setiathome_6.03_windows_intelx86.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>setigraphics_6.03_windows_intelx86.exe</file_name> <open_name>graphics_app</open_name> </file_ref> <file_ref> <file_name>libfftw3f-3-1-1a_upx.dll</file_name> <open_name>libfftw3f-3-1-1a_upx.dll</open_name> </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>setiathome_6.03_windows_intelx86.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>setigraphics_6.03_windows_intelx86.exe</file_name> <open_name>graphics_app</open_name> </file_ref> <file_ref> <file_name>libfftw3f-3-1-1a_upx.dll</file_name> <open_name>libfftw3f-3-1-1a_upx.dll</open_name> </file_ref> </app_version> </app_info>


Things to Note when combining the app_info's together, use Notepad to make the app_info.xml, you only need one <app_info> opening tag at the start of the app_info, and one </app_info> closing tag at the end of the app_info,
make sure you set Notepad to Save as Type, and to use ANSI encoding, and that it is saved as app_info.xml and not app_info.xml.txt

Claggy

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 23378
Credit: 31,813,675
RAC: 24,403
Germany
Message 1366883 - Posted: 11 May 2013, 21:52:18 UTC
Last modified: 11 May 2013, 21:53:55 UTC

Your appinfo could look like this.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>setiathome_6.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<file_info>
<name>setigraphics_6.03_windows_intelx86.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>setiathome_6.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>setigraphics_6.03_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
<open_name>libfftw3f-3-1-1a_upx.dll</open_name>
</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>setiathome_6.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>setigraphics_6.03_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
<open_name>libfftw3f-3-1-1a_upx.dll</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_ATI_r1812.exe</name>
<executable/>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r1812.cl</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>
<plan_class>ati13ati</plan_class>
<cmdline>-instances_per_device 2 -unroll 10 -ffa_block 6144 -ffa_block_fetch 1536</cmdline>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1812.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1812.cl</file_name>
<copy_file/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r1817.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 40 -instances_per_device 2-sbs 192</cmdline>
<flops>509408724.212160</flops>
<file_ref>
<file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r1817.cl</file_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
</app_version>
</app_info>
____________

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1367052 - Posted: 12 May 2013, 8:57:35 UTC

Thank you for the hints -

Let me make it clear - the

AP6_win_x86_SSE2_OpenCL_ATI_r1812.7z
MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.7z

I mentioned in the above message are not the executables - they're the compressed files found at: Update for ATi MB&AP GPU apps.
Also my CPU is an AMD Opteron 185 (2.6GHz, pni - SSE3 capable...)

***

OK -
I've jumped in. Only to find the same behavior as before - lots of CPU activity but almost no GPU work registering on 'GPU-Z.0.7.0.exe'. I think GPU-Z may be failing to get through the new Catalyst 13.4 drivers because it looks like the Astropule WUs are only going to take about 2 1/2 hours each.
Is that about right for

ap_24jl11ad_B1_P1_00331_20130511_27868.wu
ap_23ap11ab_B5_P0_00368_20130511_31436.wu

on a pair of ATI HD6950's? Or is it the CPU making a meal of them by itself?

***

The message:

12/05/2013 06:50:32 | SETI@home | [error] State file error: missing application file libfftw3f-3.dll

was reported despite the DLL existing in

C:\ProgramData\BOINC\projects\setiathome.berkeley.edu

And

12/05/2013 06:50:32 | SETI@home | [error] State file error: duplicate app version: setiathome_enhanced windows_x86_64 603

- maybe because I wove in Claggy's CPU only 'app_info.xml' example file?

***

The existing WUs were grabbed by the Optimised MB app, thus -

12/05/2013 06:51:02 | SETI@home | Starting task 08oc11af.7014.8250.5.11.181_3 using setiathome_enhanced version 700 (ati_opencl_sah) in slot 1

But all produced errors, for example -

Status Run CPU Credit Application time time ---------------------------------------------------------------------------------------------------- Error while computing 5.71 2.30 --- SETI@home Enhanced Anonymous platform (ATI GPU)


The 700 in the line above above is simply the number I put in the 'app_info.xml' file:

.
<app>
<name>setiathome_enhanced</name>
</app>
.
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</name>
<executable/>
</file_info>
.
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>700</version_num>
.
.

- because of the MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe name of the executable. Does the <version_num /> have any real effect? Or just cosmetics...

***

Despite the 'duplicate app .. 603' conflict, BOINC dloaded a few version 6.03 MultiBeam WUs and assinged them OK -

12/05/2013 06:50:53 | SETI@home | Starting task 28my12ab.18293.106923.10.11.206.vlar_2 using setiathome_enhanced version 603 in slot 3

- with an estimated 15 hour ttc.

Again - I'm not used to seeing WUs take so long. With Cat 12.8, an AP would take about an hour and an MB between 2 - 7 hours... Am I looking at a new set of 'longer' WUs?

Thanks -



____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4048
Credit: 32,693,237
RAC: 546
United Kingdom
Message 1367056 - Posted: 12 May 2013, 9:38:09 UTC - in response to Message 1367052.
Last modified: 12 May 2013, 9:39:51 UTC

Thank you for the hints -

Let me make it clear - the

AP6_win_x86_SSE2_OpenCL_ATI_r1812.7z
MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.7z

I mentioned in the above message are not the executables - they're the compressed files found at: Update for ATi MB&AP GPU apps.
Also my CPU is an AMD Opteron 185 (2.6GHz, pni - SSE3 capable...)

Use 7zip to uncompress them.

***

OK -
I've jumped in. Only to find the same behavior as before - lots of CPU activity but almost no GPU work registering on 'GPU-Z.0.7.0.exe'. I think GPU-Z may be failing to get through the new Catalyst 13.4 drivers because it looks like the Astropule WUs are only going to take about 2 1/2 hours each.
Is that about right for

ap_24jl11ad_B1_P1_00331_20130511_27868.wu
ap_23ap11ab_B5_P0_00368_20130511_31436.wu

on a pair of ATI HD6950's? Or is it the CPU making a meal of them by itself?

The AP you did has reasably High Blanking, the Blanking is done on the CPU, the more Blanking the more CPU time, and the less GPU load.

***

The message:

12/05/2013 06:50:32 | SETI@home | [error] State file error: missing application file libfftw3f-3.dll

was reported despite the DLL existing in

C:\ProgramData\BOINC\projects\setiathome.berkeley.edu

It might have existed, but Boinc will delete Stock files if you move to an app_info that doesn't have them mentioned.

And

12/05/2013 06:50:32 | SETI@home | [error] State file error: duplicate app version: setiathome_enhanced windows_x86_64 603

- maybe because I wove in Claggy's CPU only 'app_info.xml' example file?

You didn't need my CPU app_info section and Mike's app_info section, My intention was you used my app_info section and the two app_info sections supplied with the two apps you're downloaded.

***

The existing WUs were grabbed by the Optimised MB app, thus -

12/05/2013 06:51:02 | SETI@home | Starting task 08oc11af.7014.8250.5.11.181_3 using setiathome_enhanced version 700 (ati_opencl_sah) in slot 1

But all produced errors, for example -

Status Run CPU Credit Application time time ---------------------------------------------------------------------------------------------------- Error while computing 5.71 2.30 --- SETI@home Enhanced Anonymous platform (ATI GPU)

The error's occured because Mike's app_info didn't mention the libfftw3f-3.dll file, so Boinc deleted it, and the Wu's errored because it wasn't there.

The 700 in the line above above is simply the number I put in the 'app_info.xml' file:

.
<app>
<name>setiathome_enhanced</name>
</app>
.
<file_info>
<name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</name>
<executable/>
</file_info>
.
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>700</version_num>
.
.

- because of the MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe name of the executable. Does the <version_num /> have any real effect? Or just cosmetics...

***

Despite the 'duplicate app .. 603' conflict, BOINC dloaded a few version 6.03 MultiBeam WUs and assinged them OK -

12/05/2013 06:50:53 | SETI@home | Starting task 28my12ab.18293.106923.10.11.206.vlar_2 using setiathome_enhanced version 603 in slot 3

- with an estimated 15 hour ttc.

Again - I'm not used to seeing WUs take so long. With Cat 12.8, an AP would take about an hour and an MB between 2 - 7 hours... Am I looking at a new set of 'longer' WUs?

Thanks -





Claggy

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1367058 - Posted: 12 May 2013, 9:46:56 UTC - in response to Message 1367056.
Last modified: 12 May 2013, 9:47:53 UTC

Thank you very much Claggy. That is extremely helpful. Your knowledge restores a great deal of faith. - Thanks!

Guy
____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4048
Credit: 32,693,237
RAC: 546
United Kingdom
Message 1367059 - Posted: 12 May 2013, 9:53:16 UTC - in response to Message 1367052.

This is a proper fully constructed app_info, using my CPU app_info, and the app_info's from the AP6_win_x86_SSE2_OpenCL_ATI_r1812.7z and MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.7z achieves:

<app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>setiathome_6.03_windows_intelx86.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-1-1a_upx.dll</name> <executable/> </file_info> <file_info> <name>setigraphics_6.03_windows_intelx86.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>setiathome_6.03_windows_intelx86.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>setigraphics_6.03_windows_intelx86.exe</file_name> <open_name>graphics_app</open_name> </file_ref> <file_ref> <file_name>libfftw3f-3-1-1a_upx.dll</file_name> <open_name>libfftw3f-3-1-1a_upx.dll</open_name> </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>setiathome_6.03_windows_intelx86.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>setigraphics_6.03_windows_intelx86.exe</file_name> <open_name>graphics_app</open_name> </file_ref> <file_ref> <file_name>libfftw3f-3-1-1a_upx.dll</file_name> <open_name>libfftw3f-3-1-1a_upx.dll</open_name> </file_ref> </app_version> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3.dll</name> <executable/> </file_info> <file_info> <name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</name> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>610</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>ati_opencl_sah</plan_class> <cmdline></cmdline> <coproc> <type>ATI</type> <count>1</count> </coproc> <file_ref> <file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>610</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_ati_sah</plan_class> <cmdline></cmdline> <coproc> <type>ATI</type> <count>1</count> </coproc> <file_ref> <file_name>MB7_win_x86_SSE_OpenCL_ATi_HD5_r1817.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE_OpenCL_ATi_HD5.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app> <name>astropulse_v6</name> </app> <file_info> <name>AP6_win_x86_SSE2_OpenCL_ATI_r1812.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3.dll</name> <executable/> </file_info> <file_info> <name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</name> </file_info> <app_version> <app_name>astropulse_v6</app_name> <version_num>604</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>ati_opencl_100</plan_class> <cmdline></cmdline> <coproc> <type>ATI</type> <count>1</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1812.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name> <open_name>ap_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>astropulse_v6</app_name> <version_num>604</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_ati_100</plan_class> <cmdline></cmdline> <coproc> <type>ATI</type> <count>1</count> </coproc> <file_ref> <file_name>AP6_win_x86_SSE2_OpenCL_ATI_r1812.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3.dll</file_name> </file_ref> <file_ref> <file_name>ap_cmdline_win_x86_SSE2_OpenCL_ATI.txt</file_name> <open_name>ap_cmdline.txt</open_name> </file_ref> </app_version> </app_info>


If you want to apply cmdline parameters to the apps, put them in the ap_cmdline_*.txt and mb_cmdline_*.txt files rather than the app_info, then you can change parameters without having to restart Boinc.

Claggy

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1367069 - Posted: 12 May 2013, 10:56:49 UTC - in response to Message 1367059.
Last modified: 12 May 2013, 10:57:43 UTC

That is very kind of you to cobble that up. It works a treat!

The GPUs - when they have the full attention of the CPUs - crunch 6.10 apps to around 75% of their capacity, and without that un-nerving CPU overhead. When the CPUs are occupied, with 6.03 apps, the GPUs still manage a healthy 55%. That's great. It's going to be fun experimenting with balancing the power.
Initial observations are showing lightning fast GPU work!

Thanks very much,

Guy
____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4048
Credit: 32,693,237
RAC: 546
United Kingdom
Message 1367070 - Posted: 12 May 2013, 11:07:38 UTC - in response to Message 1367069.

That is very kind of you to cobble that up. It works a treat!

The GPUs - when they have the full attention of the CPUs - crunch 6.10 apps to around 75% of their capacity, and without that un-nerving CPU overhead. When the CPUs are occupied, with 6.03 apps, the GPUs still manage a healthy 55%. That's great. It's going to be fun experimenting with balancing the power.
Initial observations are showing lightning fast GPU work!

Thanks very much,

Guy

You might want to only compute on 50% of your cores, then your most productive device will compute faster.
(There is/was a feature of the Driver/apps where when the CPU was fully utilised, the AMD/ATI OpenCL apps would randomly compute slower, so we recommend at least one CPU core being left idle)

Claggy

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1368479 - Posted: 16 May 2013, 16:18:56 UTC

Hello,
Are there any command line parameters for the stock CPU app 'setiathome_enhanced 603'? I ask because - during the seti servers maintenance I ran out of gpu work so only a '603 was running. It was spread out over both cores. Maybe it runs faster this way? In which case good. But I thought it'ld be a good idea to constrain the app to one core.
Thanks -
____________

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 23378
Credit: 31,813,675
RAC: 24,403
Germany
Message 1368487 - Posted: 16 May 2013, 16:36:58 UTC

No, i`m afraid.
No switches for CPU apps yet.

____________

Profile Guy
Avatar
Send message
Joined: 17 May 99
Posts: 66
Credit: 6,969,711
RAC: 16,213
United Kingdom
Message 1368488 - Posted: 16 May 2013, 16:40:27 UTC - in response to Message 1368487.

I see. - Whoops! Putting it all back to normal....
Thanks.
____________

Tom
Send message
Joined: 12 Aug 11
Posts: 114
Credit: 4,566,097
RAC: 0
United States
Message 1368506 - Posted: 16 May 2013, 17:36:52 UTC
Last modified: 16 May 2013, 17:38:24 UTC

so only a '603 was running. It was spread out over both cores. Maybe it runs faster this way? In which case good. But I thought it'ld be a good idea to constrain the app to one core.


Is there any difference between using a command line param(if one exists)
and using processlasso or task manager to set affinity for a CPU only process?

Windows likes to spread the heat over multiple cores on the chip and will by default reschedule a process across multiple cores.

If you want to have a huge differential in heat transfer across your cores
task manager or process lasso can do it.

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 4048
Credit: 32,693,237
RAC: 546
United Kingdom
Message 1368527 - Posted: 16 May 2013, 17:59:14 UTC - in response to Message 1368479.

Hello,
Are there any command line parameters for the stock CPU app 'setiathome_enhanced 603'? I ask because - during the seti servers maintenance I ran out of gpu work so only a '603 was running. It was spread out over both cores. Maybe it runs faster this way? In which case good. But I thought it'ld be a good idea to constrain the app to one core.
Thanks -

Yes, in fact there is a command switch for the Stock 6.03 app, it is the -verb(ose) switch, it prints out the the full optimum function choices the app tested, and not just the chosen ones:

Can't set up shared mem: -1 Will run in standalone mode. setiathome_enhanced 6.02 DevC++/MinGW libboinc: 6.3.6 Work Unit Info: ............... WU true angle range is : 0.008955 Optimal function choices: ----------------------------------------------------- name ----------------------------------------------------- v_BaseLineSmooth (no other) v_GetPowerSpectrum 0.00011 0.00000 test v_vGetPowerSpectrum 0.00004 0.00000 test v_vGetPowerSpectrum2 0.00005 0.00000 test v_vGetPowerSpectrumUnrolled 0.00004 0.00000 test v_vGetPowerSpectrumUnrolled2 0.00005 0.00000 test v_vGetPowerSpectrumUnrolled 0.00004 0.00000 choice v_ChirpData 0.00419 0.00000 test fpu_ChirpData 0.00897 0.00000 test v_vChirpData_x86_64 0.08897 0.00002 test sse1_ChirpData_ak 0.00535 0.00000 test sse2_ChirpData_ak 0.00766 0.00000 test sse3_ChirpData_ak 0.00595 0.00000 test v_ChirpData 0.00419 0.00000 choice v_Transpose 0.00223 0.00000 test v_Transpose2 0.00279 0.00000 test v_Transpose4 0.00132 0.00000 test v_Transpose8 0.00246 0.00000 test v_pfTranspose2 0.00233 0.00000 test v_pfTranspose4 0.00157 0.00000 test v_pfTranspose8 0.00281 0.00000 test v_vTranspose4 0.00072 0.00000 test v_vTranspose4np 0.00072 0.00000 test v_vTranspose4ntw 0.00599 0.00000 test v_vTranspose4x8ntw 0.00443 0.00000 test v_vTranspose4x16ntw 0.00215 0.00000 test v_vpfTranspose8x4ntw 0.00613 0.00000 test v_vTranspose4np 0.00072 0.00000 choice FPU opt folding 0.00230 0.00000 test AK SSE folding 0.00069 0.00000 test BH SSE folding 0.00075 0.00000 test AK SSE folding 0.00069 0.00000 choice Flopcounter: 1938958567301.485800 Spike count: 0 Pulse count: 1 Triplet count: 0 Gaussian count: 0 called boinc_finish


Claggy

Message boards : Number crunching : Catalyst 13.4

Copyright © 2014 University of California