Forum > GPU crunching
It works!
Yellow_Horror:
I delete my cc_config.xml and feed the BOINC v.6.6.10 with such app_info.xml:
--- Quote ---<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_mod_CUDA_V9.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<file_info>
<name>AK_v8_win_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8_win_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V9.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>
</app_info>
--- End quote ---
Now it crunch 2 Seti MB 6.03 on the CPU and one Seti MB 6.08 on CUDA. I even can use "Use GPU while computer is in use" switch! This is a workaround i needed for all time since CUDA version of Seti first appears (because i don't like video lags while i work or play games). The only trouble remains is to suspend CUDA while i watch DVD video, so BOINC detect no "user activity".
Any suggestions about how to fix this issue (and any other suggestions) are welcome.
P.S. Still hope to see non-laggy CUDA app in the future, even if it will be not so fast.
Jason G:
--- Quote from: Yellow_Horror on 24 Feb 2009, 04:50:31 am ---Now it crunch 2 Seti MB 6.03 on the CPU and one Seti MB 6.08 on CUDA. I even can use "Use GPU while computer is in use" switch! This is a workaround i needed for all time since CUDA version of Seti first appears (because i don't like video lags while i work or play games). The only trouble remains is to suspend CUDA while i watch DVD video, so BOINC detect no "user activity".
Any suggestions about how to fix this issue (and any other suggestions) are welcome.
P.S. Still hope to see non-laggy CUDA app in the future, even if it will be not so fast.
--- End quote ---
Hi Yellow_Horror,
Can you confirm that it now, when downloads new work, isn't constrained to marking the highest version only with optimised app info you show? Will give it a try shortly to see for myself, but definite progress.
My suggestion for lagging during video, would be to add your media player programs, and games, to the exclusive apps entries in cc_config, though that would of course stop processing on CPUs too.
Jason
Yellow_Horror:
--- Quote from: Jason G on 24 Feb 2009, 04:58:57 am --- Can you confirm that it now, when downloads new work, isn't constrained to marking the highest version only with optimised app info you show? Will give it a try shortly to see for myself, but definite progress.
--- End quote ---
Sorry, can't check it now because now i have lot of WUs downloaded by stock apps when i first run new BOINC. Maybe few hours later i can answer the question.
Thank you for your suggestion also, but i never wish to suspend Seti CPU applications. They always are user-gentle since i enter the project at june 2003.
Jason G:
Yeah, tough new growing pains! ... Now I have it set up similar to yours, but with no multibeams in cache, so I'll find out when I can get some new cuda work, exactly what it does.
Jason
[Edit:]
Just checked the Boinc logs, and no mentions of anonymous platform behaviour changes, so my suspicion is the operation will be the same as 6.6.9 and earlier, which had stock separate CPU & GPU work fetches working properly, but when switching to app_info will mark all [newly fetched] work as 6.08 (but I'll wait and see)
The one major change that IS helpful was applied in 6.6.9 . When tasks marked with an older revision run out, it no longer deletes the old app, if it is marked with a different plan_class . That is good, because for my own use it enabled me to manually give my cpu app a new application name in app_info, then modify client_state to allocate chosen tasks to CPU to work on simualtaneously with cuda ones. Works very well for me, but not for the beginner or faint of heart! :)
Yellow_Horror:
I notice that in my new config the CUDA app freeze sometimes at the beginning of a WU. The CPU time stops at 3 second and the GPU is totally idle. Suspending the freezed task don't help - no new CUDA task starts. Stop and restart BOINC help - until next freeze. I don't have such trouble with "V8a team" mod on BOINC 6.4.5 but remember something like with the early stock CUDA apps (but IIRC suspending a task helps with stock).
What may be the cause?
Navigation
[0] Message Index
[#] Next page
Go to full version