Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 40
Posts: 40   Pages: 4   [ Previous Page | 1 2 3 4 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 28693 times and has 39 replies Next Thread
RaymondFO
Veteran Cruncher
USA
Joined: Nov 30, 2004
Post Count: 561
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

FYI, I got a work unit that is a little long. A Pentium 4 3.4g computer is projected to complete a HCMD2 WU just under 40 hours. Should I abort or let it run and see what happens? The computer is back to NRW after this WU is completed or aborted.
----------------------------------------
[Edit 1 times, last edit by RaymondFO at May 13, 2009 12:43:07 AM]
[May 13, 2009 12:39:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3715
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

Raymond,
Simply ignore the estimated time to complete and keep an eye on it. It should complete in a few hours only (much less than NRW). The last one that has completed in my P4 running in HT mode has taken 3.25 hours. And my P4 HT is only a 2.4 GHz one. smile
And the estimated TTC for the queued ones is still at 18:40 hours after completing a few!

Happy crunching. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[May 13, 2009 1:13:54 AM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

Please let the work units run. There may be work units that run long. The temporary solution to get rid of the 200 hour work units that ran during the beta was to split the work unit into 1/10th the size. This would mean that members MAY see work units that are 20 hours in length.

Jean is correct, the estimations are going to be off as it is a new project. Most new projects have this issue.

-Uplinger
[May 13, 2009 2:46:48 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

I've finished a few work units on my mac book in 4 minutes. hmmm.
[May 13, 2009 3:00:06 AM]   Link   Report threatening or abusive post: please login first  Go to top 
wplachy
Senior Cruncher
Joined: Sep 4, 2007
Post Count: 423
Status: Offline
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

Wasn't sure if I should post this here or start a new thread since this now seems to be about short, long and overall project but will try it here.

I've completed 6 WU in the last 30 minutes. All but 1 on an I7 P920. The WUs are running 8 - 10 minutes of CPU time. All show status of "Pending Validation" and all have the same "Status"

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
called boinc_finish

</stderr_txt>
]]>

So it does not appear they have "errored out". The WUs are:

Result Name & CPU
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 3219_ 1-- CPU 0.15
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 2646_ 0-- CPU 0.16
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 2655_ 1-- CPU 0.14
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 2345_ 0-- CPU 0.26
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 1995_ 0-- CPU 0.15
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 1099_ 0-- CPU 0.13

Should these really be running only 8 minutes?
----------------------------------------
Bill P

[May 13, 2009 3:13:55 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

These shorties are doing wonders for my total number of WU and my average time per WU.
[May 13, 2009 3:16:30 AM]   Link   Report threatening or abusive post: please login first  Go to top 
wplachy
Senior Cruncher
Joined: Sep 4, 2007
Post Count: 423
Status: Offline
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

These shorties are doing wonders for my total number of WU and my average time per WU.


Yea, but heck to pay for a badge biggrin

------------------------------------------------------
Bill P
----------------------------------------
Bill P

[May 13, 2009 3:19:48 AM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

Wasn't sure if I should post this here or start a new thread since this now seems to be about short, long and overall project but will try it here.

I've completed 6 WU in the last 30 minutes. All but 1 on an I7 P920. The WUs are running 8 - 10 minutes of CPU time. All show status of "Pending Validation" and all have the same "Status"

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
called boinc_finish

</stderr_txt>
]]>

So it does not appear they have "errored out". The WUs are:

Result Name & CPU
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 3219_ 1-- CPU 0.15
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 2646_ 0-- CPU 0.16
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 2655_ 1-- CPU 0.14
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 2345_ 0-- CPU 0.26
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 1995_ 0-- CPU 0.15
CMD2_ 0001-GPDAA.clustersOccur-RADIA.clustersOccur_ 1099_ 0-- CPU 0.13

Should these really be running only 8 minutes?


It appears that the combination between protein GPDAA and RADIA got chopped up more than other work units. These work units should have all been sent out. There is a possibility that more will appear. But this combination should all have been sent out to the members machines.

-Uplinger
[May 13, 2009 3:26:58 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3715
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

Jean is correct, the estimations are going to be off as it is a new project. Most new projects have this issue.

Keith,
It's also (or more) that running NRW in dual mode on a P4 HT is throwing the DCF to the sky. Every time I have run a WU of another project after a period of double Rice crunching on my P4 HT I have seen estimates extremely overestimated.
Once you know it you just have to ignore it. smile

Cheers. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[May 13, 2009 4:11:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
RaymondFO
Veteran Cruncher
USA
Joined: Nov 30, 2004
Post Count: 561
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Return time of a HCMD2 WU half as normal?

Thank you the responce and clarification. The projected 40 hour WU result is as follows:

CMD2_ 0001-GPDAA.clustersOccur-MYH6.clustersOccur_ 702_ Pending Validation 5/12/09 20:57:25 5/13/09 06:32:45 2.30 17.0 / 0.0.

2.30 hours is never an issue.
[May 13, 2009 10:13:25 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 40   Pages: 4   [ Previous Page | 1 2 3 4 ]
[ Jump to Last Post ]
Post new Thread