Forum > Windows
app_info optimise guide help wanted
Skywalker66_Bln:
Can anyone help me or have good tips for
Quad-Core 64 bit
Dual-Core 32 bit
all run under Boinc 6.10.43 and Cuda 2.3 and MB_6.08_CUDA_V12_VLARKill_FPLim2048
for Gpu:
as 609
Ncpus 0,15 or 0,127970 or ?????
Calculation factor peak<gflops>/5,6 *0,5 ? on one system i have many trouble , gpu times goes higher and higher. Anyone tell me peak<gflops>/5,6
Lunatics installer brings no better results
Thanks for help
Ghost0210:
Hi Skywalker66_Bln,
Here's a copy of my app_info,
I run a quad core AMD Phenom black
with a GTX260 and GT240 GPU
on 64-Bit Win7 machine running the vLar NoKill app
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_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>
<flops>5700000000</flops>
<file_ref>
<file_name>AK_v8b_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_v8b_win_SSE3_AMD.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.05r339_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<flops>7589595748</flops>
<file_ref>
<file_name>ap_5.05r339_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<flops>7589595748</flops>
<file_ref>
<file_name>ap_5.05r339_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.08_CUDA_V12_noKill_FPLim2048.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>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<flops>40000000000</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_noKill_FPLim2048.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_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<flops>40000000000</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_noKill_FPLim2048.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_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<flops>40000000000</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_noKill_FPLim2048.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_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<flops>40000000000</flops>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.08_CUDA_V12_noKill_FPLim2048.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>
You may want to trim it down as I've just left it pretty much the same as the v0.35 installer has it, just added in the flops for the CPU and GPU
Hope this helps
Skywalker66_Bln:
the again writing with <plan_class>cuda23</plan_class> i have no seen before or i have not noticed
a new test can start,
ups all Cudas are lost and the server is in maintaince ..... lol.... why can i not wait ????? lol
when i am on the 64 bits, i insert the 64bit lines, i dont have (before i dont spezify to 64 bit, only the 64bit drivers)
Ghost0210:
lost all my wu's many times :(
now make backup of Boinc directory and set Boinc mngr to network activity suspended before testing anything
if your GPU timews are going up, then I doubt it would be a app_info issue
as long as you chose the correct installer from here and the correct CPU etc then the app_info will be made for you, all you have to do is to add in the flops line. As far as I know the flops just changes the estimated time for the cuda wu's to be more realistic.
If you aren't seeing any imporvemtn with the Lunatics installer then I would have a look at the GPU and make sure it is running correctly
Claggy:
Try the Lunatics Beta Installer, it'll install the latest apps, do the app_info properly,
rebrand MB 6.09 Wu's to 6.08 so you don't loose any Wu's (and for use with the reschedule1.9 tool),
then all you have to do is add flops values according to MarkJ's formula.
make sure you post feedback in Beta Installer thread.
Claggy
Navigation
[0] Message Index
[#] Next page
Go to full version