BOINC 6.10.58 incorrect running time estimation

Forum > Discussion Forum

(1/4) > >>

Raistmer:
On my NV host newly recived GPU tasks always get time estimation ~2h (just as CPU ones) though real elapsed time ~30 minutes or less.
In the past I ran re-scheduler on this host but it was not running few months (!) already.
And estimation time still hugely incorrect.
It prevents host from downloading enough work to allow running with disabled network for statistic collection...

Please, any advices how it can be fixed w/o BOINC upgrade?

EDIT: it does correction for already downloaded time, but when fresh tasks arrive they have huge estimation again...
app_info is:

--- Quote ---<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSSE3x.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>AK_v8b2_win_x64_SSSE3x.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_v8b2_win_x64_SSSE3x.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41g_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda_fermi</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>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda23</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>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>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>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda_fermi</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>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda23</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>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
</app_info>

--- End quote ---

Raistmer:
ADDON:

SETI@home Enhanced (anonymous platform, CPU)
Number of tasks completed   4527
Max tasks per day   228
Number of tasks today   0
Consecutive valid tasks   129
Average processing rate   17.686758629915
Average turnaround time   8.77 days
SETI@home Enhanced (anonymous platform, nvidia GPU)
Number of tasks completed   14106
Max tasks per day   675
Number of tasks today   0
Consecutive valid tasks   576
Average processing rate   255.03870331506
Average turnaround time   6.36 days

Claggy:
Eithier bother DA or Eric to fix the server side Estimates for Anonymous Platform users that aren't using flops entries,

or put flops into your app_info (use the APR figure with e09 at the end), eg 17.686758629915e09 for CPU MB app & 255.03870331506e09 for Nvidia GPU MB app,

or use Jason's 6.10.58 boinc.exe,

Claggy

Mike:
I have the same issue with GPU times ETA since i removed flops entry.
So long i get enough work i dont care.
But its funny at least.
I remember Joe telling me at main it will correct itself.
Maybe in 100 years.

Mike

Richard Haselgrove:

--- Quote from: Raistmer on 08 Feb 2012, 08:25:00 am ---On my NV host newly recived GPU tasks always get time estimation ~2h (just as CPU ones) though real elapsed time ~30 minutes or less.
In the past I ran re-scheduler on this host but it was not running few months (!) already.
And estimation time still hugely incorrect.
It prevents host from downloading enough work to allow running with disabled network for statistic collection...

Please, any advices how it can be fixed w/o BOINC upgrade?

--- End quote ---

That's not a client issue - it's the result of server changeset 24128, much discussed on the SETI message boards since 05 September 2011.

Options are:

* Only run one application type at a time (probably advisable for statistical collection anyway)
* Populate app_info with appropriate <flops> values for every app specified
* Use Jason's aDCF client variant
* Join us in lobbying DA and SETI staff to restore the server configuration to documented operating mode - safely

Navigation

[0] Message Index

[#] Next page

Go to full version