I think it will be a few years before "Average processing rate  
147528.27256404"
is possible. Yet that's what's shown for a host which was attached to s...@h  
two
days ago to do Astropulse v505 work. Text copies of the Application  
details and
the one Astropulse validated task are below, the first could change soon  
and
the second disappear soon.

The task took 89,037.14 seconds, and Astropulse tasks have rsc_fpops_est of
1.82105211446231e+15 so I calculate it should have gotten 20.452724722 for  
the
"Average processing rate" (et.avg ~ 4.89e-11). Being off by a factor over  
7000
means even if the next nine validations are correctly averaged in, the  
rate will
still be high by a factor of more than 50 when tasks with scaled fpops  
estimates
and bounds are sent to the host. The rsc_fpops_bound values will give an
impossible max_elapsed_time.

I hope this is just a glitch which happened to hit that host and there's  
some
way to fix its data.
-- 
                                                          Joe


===========================================================
Application details for host 5714799    

HOME    PARTICIPATE     ABOUT   COMMUNITY       ACCOUNT STATISTICS

s...@home Enhanced 6.03 windows_intelx86
Number of tasks completed       0
Max tasks per day       99
Number of tasks today   0
Consecutive valid tasks 0
Average turnaround time 0.00 days

Astropulse v505 5.05 windows_intelx86
Number of tasks completed       3
Max tasks per day       101
Number of tasks today   0
Consecutive valid tasks 1
Average processing rate 147528.27256404
Average turnaround time 0.03 days

HOME    PARTICIPATE     ABOUT   COMMUNITY       ACCOUNT STATISTICS
Copyright c 2010 University of California

===========================================================

Task 1755709879 

HOME    PARTICIPATE     ABOUT   COMMUNITY       ACCOUNT STATISTICS

Name    ap_18au10ab_B5_P0_00098_20101226_02602.wu_0
Workunit        673683034
Created 26 Dec 2010 9:06:27 UTC
Sent    26 Dec 2010 15:17:03 UTC
Received        27 Dec 2010 22:03:50 UTC
Server state    Over
Outcome Success
Client state    Done
Exit status     0 (0x0)
Computer ID     5714799
Report deadline 20 Jan 2011 15:17:03 UTC
Run time        89,037.14
CPU time        88,704.52
Validate state  Valid
Credit  715.25
Application version     Astropulse v505 v5.05

Stderr output
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 896
...
[109 similar lines omitted]
...
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 14976
called boinc_finish

</stderr_txt>
]]>
HOME    PARTICIPATE     ABOUT   COMMUNITY       ACCOUNT STATISTICS
Copyright c 2010 University of California

==============================================================
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to