Einstein@home News Q1 2011
- Thread starter derk
- Start date
Soldato
Interesting, 2 of my gpu's have flat out refused to crunch seti units and are just dropping the wu's after 10 or so seconds....start up Einstein and they crunch wu's just fine 
Soldato
Have just downloaded some more Einstein WUs and am doing a trial run of having two instances on my GTS250. As I posted earlier, one WU on its own takes ~70mins and three take ~160mins between them. Unfortunately the system is pretty sluggish with three instances running but seems much better with just the two, so I may end up leaving it at that anyway.
On another note, the 48 WUs I got weighed in at a combined download size of 770MB... This project is definitely not for those with a low download limit
Have you checked your SETI results against others that have done the same WUs? Might just be a bad batch you downloaded. Alternatively, it might be possible that one or more of your SETI GPU apps has somehow become corrupt - try reinstalling the GPU-related apps (inc. drivers) to see if that helps. Lastly, see if something's broken in your SETI app_info file.
On another note, the 48 WUs I got weighed in at a combined download size of 770MB... This project is definitely not for those with a low download limit
Interesting, 2 of my gpu's have flat out refused to crunch seti units and are just dropping the wu's after 10 or so seconds....start up Einstein and they crunch wu's just fine
Have you checked your SETI results against others that have done the same WUs? Might just be a bad batch you downloaded. Alternatively, it might be possible that one or more of your SETI GPU apps has somehow become corrupt - try reinstalling the GPU-related apps (inc. drivers) to see if that helps. Lastly, see if something's broken in your SETI app_info file.
Last edited:
Soldato
Evening Mr T, yup have tried everything barring detach which i cannot do at the minute as i have some completed wu's that didn't break etc.
Am just going to leave it for the weekend at least until Berkeley is up n running and do a full clean sweep early in the week. Going to take a wander over to sunny Preston for the weekend i think.
Am just going to leave it for the weekend at least until Berkeley is up n running and do a full clean sweep early in the week. Going to take a wander over to sunny Preston for the weekend i think.
Soldato
In that case, unless a complete detach/reattach solves the problem, the only other thing I can think of is that it might be an issue with the card (touches wood it isn't!). We all know that SETI pushes GPUs harder than Einstein (in terms of GPU usage, at least), but even then I'd assume that the problem would be apparent in any project you ran on it.
As a test, have you run folding on it? That seems to stress the card even more than SETI does, so I'd imagine any stability problems would surface pretty quickly.
As a test, have you run folding on it? That seems to stress the card even more than SETI does, so I'd imagine any stability problems would surface pretty quickly.
Soldato
Right, two Einstein WUs have now finished with a completion time of ~110mins each.
Comparison:
Running one instance = 70mins
Running two instances = 110mins
Running three instances = 160mins
Extrapolating for six WUs:
Running one instance = 420mins
Running two instances = 330mins
Running three instances = 320mins
In short, there's a big difference between running one instance of the app and running two but a much smaller difference between running two instances and three, so I'm happy to leave it at two, particularly given the increased lag I get when three instances are run.
Comparison:
Running one instance = 70mins
Running two instances = 110mins
Running three instances = 160mins
Extrapolating for six WUs:
Running one instance = 420mins
Running two instances = 330mins
Running three instances = 320mins
In short, there's a big difference between running one instance of the app and running two but a much smaller difference between running two instances and three, so I'm happy to leave it at two, particularly given the increased lag I get when three instances are run.
Well Then.....
Water Cooloing Motherboard & CPU is completed - as far as installation goes.
Pump is running, water is flowing and no leaks - been running for a few hours now.
Just trying to decide if I should power up the MB & CPU.........
Piccies to follow - in a suitable thread.
Water Cooloing Motherboard & CPU is completed - as far as installation goes.
Pump is running, water is flowing and no leaks - been running for a few hours now.
Just trying to decide if I should power up the MB & CPU.........
Piccies to follow - in a suitable thread.
All I can say is:
Glad it was only the MB & CPU I was doing.
Took appprox 17 hours start to finish(inc food breaks etc).
Temps are approx 60 - 64c whereas they were 80(ish) with the H70 running identical tasks.
Dunno if this is good, bad or ugly.
4.2GHz (200 Bclk x 21 Multiplier) & VCore 1.382v:
http://valid.canardpc.com/show_oc.php?id=1650953
Need to do some cable management, make the cables for the UV lights and put the dye bomb in - but it's late/early and I need sleep - so it's nap time.
Will do a quick build log after doing cables etc and had a nap.
Glad it was only the MB & CPU I was doing.
Took appprox 17 hours start to finish(inc food breaks etc).
Temps are approx 60 - 64c whereas they were 80(ish) with the H70 running identical tasks.
Dunno if this is good, bad or ugly.
4.2GHz (200 Bclk x 21 Multiplier) & VCore 1.382v:
http://valid.canardpc.com/show_oc.php?id=1650953
Need to do some cable management, make the cables for the UV lights and put the dye bomb in - but it's late/early and I need sleep - so it's nap time.
Will do a quick build log after doing cables etc and had a nap.
Last edited:
Soldato
Morning TT have just set off the folding client, that should sort the little blighters out, i don't mind if a card or 2 is jiggered as they have served well and more than payed for themselves in my eyes.
Just to double check with all the gpu's running and big adv does this look right, am sort of sure but when in doubt consult the experts!
Gpu's are on 700/1400 .98 volts any higher and gpu 3 drops wu's with the "unstable machine" error, fingers crossed will leave it for a few hours.
Well done Mr Loudbob sah, working through the night and 17 hours too
Enjoy your well earned nap and best of luck with the rest, i guess all this activity will serve to kick my butt into gear and get mine done. It is a crime when i see the hardware laying around but coupled with flu and other stuff going on the time has never felt quite right.
Mind you if we get to see some snappies of your handy work that'll probably get me started, really looking forward to this
Last edited:
Soldato
Done thank you Mr Biffa, folding going a treat no hiccups Einstein the same just Seti when they're back from the brink will do a clean install with it
Associate
Yes Einstein has a cuda app and you can now use an app_info file to run multiple wu's per gpu.
If your just not getting cuda wu's look at your einstein preferences and select gpu work
If your just not getting cuda wu's look at your einstein preferences and select gpu work
Thanks BaBa where is the app_info file?
I have one GTX 460 in my rig. And it has 1 work unit and only runs 1 at a time. But the GPU usage is peaking at 55 but hovering around 50.
Are you saying I can run 2 tasks on my one 460?
I have one GTX 460 in my rig. And it has 1 work unit and only runs 1 at a time. But the GPU usage is peaking at 55 but hovering around 50.
Are you saying I can run 2 tasks on my one 460?
Last edited:
Associate
Im running 3 wu's on my 460 1gb and 2 on 460 768mb cards.
Im running this
<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__S5GCESSE2.exe</name>
<main_program/>
</file_info>
<file_info>
<name>einstein_S5R6_3.01_graphics_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_23.dll</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_23.dll</name>
<executable/>
</file_info>
<file_info>
<name>einsteinbinary_BRP3_1.04_windows_intelx86__BRP3cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>einsteinbinary_BRP3_1.05_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.4330b3e5</name>
</file_info>
<file_info>
<name>dbhs.dev.win.4330b3e5</name>
</file_info>
<file_info>
<name>db.dev.win.96b133b1</name>
</file_info>
<file_info>
<name>dbhs.dev.win.96b133b1</name>
</file_info>
<app_version>
<app_name>einsteinbinary_BRP3</app_name>
<version_num>104</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.04_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.4330b3e5</file_name>
<open_name>db.dev</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.4330b3e5</file_name>
<open_name>dbhs.dev</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>CUDA</type>
<count>0.330000</count>
</coproc>
<gpu_ram>220200960.000000</gpu_ram>
</app_version>
<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.05_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.96b133b1</file_name>
<open_name>db.dev</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.96b133b1</file_name>
<open_name>dbhs.dev</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>CUDA</type>
<count>0.330000</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_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>
</app_info>
this gives 3wu's if you want only two change the 0.330000 to 0.500000 (two places) save it as app_info.xml
Also look at http://einstein.phys.uwm.edu/forum_thread.php?id=8652#110430
Im running this
<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__S5GCESSE2.exe</name>
<main_program/>
</file_info>
<file_info>
<name>einstein_S5R6_3.01_graphics_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_23.dll</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_23.dll</name>
<executable/>
</file_info>
<file_info>
<name>einsteinbinary_BRP3_1.04_windows_intelx86__BRP3cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>einsteinbinary_BRP3_1.05_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.4330b3e5</name>
</file_info>
<file_info>
<name>dbhs.dev.win.4330b3e5</name>
</file_info>
<file_info>
<name>db.dev.win.96b133b1</name>
</file_info>
<file_info>
<name>dbhs.dev.win.96b133b1</name>
</file_info>
<app_version>
<app_name>einsteinbinary_BRP3</app_name>
<version_num>104</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.04_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.4330b3e5</file_name>
<open_name>db.dev</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.4330b3e5</file_name>
<open_name>dbhs.dev</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>CUDA</type>
<count>0.330000</count>
</coproc>
<gpu_ram>220200960.000000</gpu_ram>
</app_version>
<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.05_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.96b133b1</file_name>
<open_name>db.dev</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dbhs.dev.win.96b133b1</file_name>
<open_name>dbhs.dev</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>CUDA</type>
<count>0.330000</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_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>
</app_info>
this gives 3wu's if you want only two change the 0.330000 to 0.500000 (two places) save it as app_info.xml
Also look at http://einstein.phys.uwm.edu/forum_thread.php?id=8652#110430
Soldato
Plonk it in the einstein.phys.uwm.edu folder
Plonk it in the einstein.phys.uwm.edu folder
Cannot find this anywhere =/
I looked in program files > BOINC but there isn't anything.
Know where it defaults to?
Associate
Its goes in programdata/boinc/projects/einstein.
The program data file may be hidden but default is c drive.
The program data file may be hidden but default is c drive.
Soldato
For some reason, by default BOINC installs the data folders in a different location to everything else. This location depends on which OS you're using and the folder is hidden, so you'll need to show hidden files and folders and then do a search for 'einstein.phys.uwm.edu'. Once in there, drop your app_info in it, then stop and restart BOINC to make sure everything's working as it should.
Edit: Gah, beaten to it
Edit: Gah, beaten to it
Last edited: