Just started GPU's on Einstein

**zombie67** · 07-12-11, 09:53 PM

If I remember correctly, the GPU app still uses a LOT of CPU. And the GPU us under utilized. You will probably be better off crunching with just CPU, and using your GPU elsewhere more productive.

**Fire$torm** · 07-12-11, 10:53 PM

Originally Posted by Bryan

F$, I did a search on their forums for app_info and a couple actually showed up in the thread listings. I didn't look at them but it may give you a starting point.

Yeah I did see those. I tried them and they failed. So I have been trying to debug them since. Total crash and burn.

Now I cannot connect to the server. I think the server is blocking me because it looks like DOS attack....... Sometimes this hobby just..... sucks.

**Fire$torm** · 07-12-11, 11:06 PM

OK, this was my original app_info file based on the BOINC wiki for anonymous paltform

<app_info>
<app_version>
<app_name>einsteinbinary_BRP3</app_name>
<version_num>107</version_num>
<api_version>6.13.0</api_version>
<file_ref>
<file_name>einsteinbinary_BRP3_1.07_windows_intelx 86__BRP3cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart_xp32_32_16.dll</file_name>
<open_name>cudart32_32_16.dll</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>cufft_xp32_32_16.dll</file_name>
<open_name>cufft32_32_16.dll</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>einsteinbinary_BRP3_1.00_graphics_windo ws_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
<file_ref>
<file_name>EULA.txt</file_name>
<open_name>EULA.txt</open_name>
</file_ref>
<file_ref>
<file_name>db.dev.win.3d35195e</file_name>
<open_name>db.dev</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.3d35195e</file_name>
<open_name>dbhs.dev</open_name>
<copy_file/>
</file_ref>
<platform>windows_intelx86</platform>
<plan_class>BRP3cuda32</plan_class>
<avg_ncpus>0.200000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<flops>24320145631.746910</flops>
<coproc>
<type>CUDA</type>
<count>0.500000</count>
</coproc>
<gpu_ram>220200960.000000</gpu_ram>
</app_version>
</app_info>

I do not remember the error messages but it didn't work.

Now here is the app_info file from the Einstein forum edited for the latest CUDA app version 1.07

<app_info>
<app>
<name>einstein_S5GC1HF</name>
<user_friendly_name>Global Correlations S5 HF search #1</user_friendly_name>
</app>
<app>
<name>einsteinbinary_BRP3</name>
<user_friendly_name>Binary Radio Pulsar Search</user_friendly_name>
</app>
<file_info>
<name>einstein_S5GC1HF_3.06_windows_intelx86__S5GC ESSE2.exe</name>
<main_program/>
</file_info>
<file_info>
<name>einstein_S5R6_3.01_graphics_windows_intelx86 .exe</name>
<executable/>
</file_info>
<file_info>
<name>einsteinbinary_BRP3_1.07_windows_intelx86__B RP3cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>einsteinbinary_BRP3_1.00_graphics_windows_in telx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart_xp32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft_xp32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>dbhs.dev.win.3d35195e</name>
</file_info>
<file_info>
<name>dbhs.dev.win.3d35195e</name>
</file_info>
<app_version>
<app_name>einsteinbinary_BRP3</app_name>
<version_num>107</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.200000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<plan_class>BRP3cuda32</plan_class>
<api_version>6.13.0</api_version>
<file_ref>
<file_name>einsteinbinary_BRP3_1.07_windows_intelx 86__BRP3cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart_xp32_32_16.dll</file_name>
<open_name>cudart32_32_16.dll</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>cufft_xp32_32_16.dll</file_name>
<open_name>cufft32_32_16.dll</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>einsteinbinary_BRP3_1.00_graphics_windo ws_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.3d35195e</file_name>
<open_name>db.dev</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.3d35195e</file_name>
<open_name>dbhs.dev</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>CUDA</type>
<count>0.500000</count>
</coproc>
<gpu_ram>220200960.000000</gpu_ram>
</app_version>
<app_version>
<app_name>einstein_S5GC1HF</app_name>
<version_num>306</version_num>
<platform>windows_intelx86</platform>
<plan_class>S5GCESSE2</plan_class>
<api_version>6.13.0</api_version>
<file_ref>
<file_name>einstein_S5GC1HF_3.06_windows_intelx86_ _S5GCESSE2.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>einstein_S5R6_3.01_graphics_windows_int elx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>
</app_info>

This one generated URL errors

7/12/2011 10:08:56 PM [error] No URL for file transfer of einsteinbinary_BRP3_1.07_windows_intelx86__BRP3cud a32.exe
7/12/2011 10:08:56 PM [error] No URL for file transfer of einsteinbinary_BRP3_1.00_graphics_windows_intelx86 .exe
7/12/2011 10:08:56 PM [error] No URL for file transfer of cudart_xp32_32_16.dll
7/12/2011 10:08:56 PM [error] No URL for file transfer of cufft_xp32_32_16.dll
7/12/2011 10:08:56 PM [error] No URL for file transfer of dbhs.dev.win.3d35195e

Then I added URL references to the app_info file like I found in an app_info file posted on E@H only to discover BOINC does not allow URL references in an app_info file.

Gad Zooks Batman. Why can't projects have a section on their forums listing WORKING app_info files? It can't be THAT F'n hard. After all THEY did write the apps.

**Fire$torm** · 07-12-11, 11:09 PM

Originally Posted by zombie67

If I remember correctly, the GPU app still uses a LOT of CPU. And the GPU us under utilized. You will probably be better off crunching with just CPU, and using your GPU elsewhere more productive.

OK, you might be right. though according to the E@H forum post by the project admin(s) they say the CUDA app is 20x faster then the CPU app for the sub-project.

**Bryan** · 07-12-11, 11:18 PM

The easiest way might be to look at the projects "Top Users" and find one that identifies his tasks as anonymous platform and just PM them and ask if they would share their app_info

**Fire$torm** · 07-12-11, 11:37 PM

Originally Posted by Bryan

The easiest way might be to look at the projects "Top Users" and find one that identifies his tasks as anonymous platform and just PM them and ask if they would share their app_info

Well... DUH!!!! Why didn't you think of that? Oh, wait... you did.

OK, smart aleck, will do.

**Fire$torm** · 07-13-11, 12:41 AM

Originally Posted by Bryan

The easiest way might be to look at the projects "Top Users" and find one that identifies his tasks as anonymous platform and just PM them and ask if they would share their app_info

Originally Posted by Fire$torm

Well... DUH!!!! Why didn't you think of that? Oh, wait... you did.

OK, smart aleck, will do.

UPDATE.

Well, while looking for posts from one of the top users I found this thread 3WU BRP3cuda on a single GPU. Within that thread is message 110450. That post is the first time I have seen someone really SHOW you which sections do what. He posted an update to run version 1.07 of the CUDA app so I will post it here (I have removed the reference to version 1.05).

This is just for the CUDA app.

Code:

<app_info>
    <app>
        <name>einsteinbinary_BRP3</name>
        <user_friendly_name>Binary Radio Pulsar Search</user_friendly_name>
    </app>
    <file_info>
        <name>einsteinbinary_BRP3_1.07_windows_intelx86__BRP3cuda32.exe</name>
    <executable/>
    </file_info>
    <file_info>
        <name>einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe</name>
    <executable/>
    </file_info>
    <file_info>
        <name>cudart_xp32_32_16.dll</name>
    <executable/>
    </file_info>
    <file_info>
        <name>cufft_xp32_32_16.dll</name>
    <executable/>
    </file_info>
    <file_info>
        <name>db.dev.win.3d35195e</name>
    </file_info>
    <file_info>
        <name>dbhs.dev.win.3d35195e</name>
    </file_info>
    <app_version>
        <app_name>einsteinbinary_BRP3</app_name>
        <version_num>105</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.200000</avg_ncpus>
        <max_ncpus>1.000000</max_ncpus>
        <plan_class>BRP3cuda32</plan_class>
        <api_version>6.13.0</api_version>
    <file_ref>
        <file_name>einsteinbinary_BRP3_1.07_windows_intelx86__BRP3cuda32.exe</file_name>
    <main_program/>
    </file_ref>
    <file_ref>
        <file_name>cudart_xp32_32_16.dll</file_name>
        <open_name>cudart32_32_16.dll</open_name>
    <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>cufft_xp32_32_16.dll</file_name>
        <open_name>cufft32_32_16.dll</open_name>
    <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe</file_name>
        <open_name>graphics_app</open_name>
    </file_ref>
    <file_ref>
        <file_name>db.dev.win.3d35195e</file_name>
        <open_name>db.dev</open_name>
    <copy_file/>
    </file_ref>
    <file_ref>
        <file_name>dbhs.dev.win.3d35195e</file_name>
        <open_name>dbhs.dev</open_name>
    <copy_file/>
    </file_ref>
    <coproc>
        <type>CUDA</type>
        <count>0.500000</count>
    </coproc>
        <gpu_ram>220200960.000000</gpu_ram>
    </app_version>
</app_info>

Sorry but I cannot test it now since the Einstein server is blocking my connections. I'll have to wait until the firewall times out my supposed "attack".

**Mad Matt** · 07-13-11, 06:10 PM

Originally Posted by Fire$torm

OK, you might be right. though according to the E@H forum post by the project admin(s) they say the CUDA app is 20x faster then the CPU app for the sub-project.

If that's right they tuned down GPU credits artificially, but I have some doubts about that. I just made some short efforts with a GTX 295 quite a while ago, and it hardly tops three Quads/i7s, so indeed return is more than lousy compared to usual GPU projects. For me it's still a CPU project and within the 'normal' range it has a quite competitive return for CPUs.

**Fire$torm** · 07-13-11, 08:43 PM

Originally Posted by Mad Matt

If that's right they tuned down GPU credits artificially, but I have some doubts about that. I just made some short efforts with a GTX 295 quite a while ago, and it hardly tops three Quads/i7s, so indeed return is more than lousy compared to usual GPU projects. For me it's still a CPU project and within the 'normal' range it has a quite competitive return for CPUs.

Ahhhhh. OK. I see. Ya know I have a new term for bad GPU credits ---> The DA Effect <----

Its my thought and I'm sticking to it.........

**Bryan** · 07-14-11, 12:10 AM

Originally Posted by Fire$torm

Ahhhhh. OK. I see. Ya know I have a new term for bad GPU credits ---> The DA Effect <----

Its my thought and I'm sticking to it.........

Sounds quite intelligent to me!

Thread: Just started GPU's on Einstein

Thread Tools

Display

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Re: Just started GPU's on Einstein

Posting Permissions