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: 6
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1910 times and has 5 replies Next Thread
sgoll
Advanced Cruncher
Joined: Oct 24, 2006
Post Count: 87
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
I'm wondering ...

Is there a runtime limit on (H)CMD2 workunits? I'm getting some strange results like this:

Result Name: CMD2_ 0453-KU70A.clustersOccur-2BOV_ B.clustersOccur_ 3_ 26180_ 26778_ 1--
<core_client_version>6.10.44</core_client_version>
<![CDATA[
<stderr_txt>
INFO: Initializing Platform.
INFO: No state to restore. Start from the beginning.
Finishing early because max runtime has been exceeded.23853.020000
called boinc_finish

</stderr_txt>
]]>

After nearly 6 hours of crunching ... Of course this cruncher is not the fastet one, it's a 500 MHz AMD Geode, but he crunches reliable. FAAH und HFCC workunits took up to 4 days, but thats okay für a router box that is running 7/24.
So ... if there is a runtime limit on the CMD2 workunits, how can I get around this limit? Or should I disable the complete support für CMD2 only because I user a cruncher that is a bit slow?
Stephan
----------------------------------------

[May 11, 2010 12:11:53 PM]   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: I'm wondering ...

Yes, there are runtime limits on HCMD2 WUs.
If you are not more than 60% comlpete after 6 hours it will stop and return the results you have processed. If you are more than 60% done at 6 hours it will conitnue until it is complete or you have been processing for 12 hours at which time it will also stop and return the results you have processed. You can not get around the limits. The crunching you do are valid and will be used so it is up to you if you want to continue contribute to this project or focus on others.

Regards,
Steve
----------------------------------------
[Edit 2 times, last edit by Former Member at May 11, 2010 12:18:16 PM]
[May 11, 2010 12:16:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
martin64
Senior Cruncher
Germany
Joined: May 11, 2009
Post Count: 445
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: I'm wondering ...

should I disable the complete support für CMD2 only because I user a cruncher that is a bit slow?

Maybe. blushing
What you can do is wath out for the result status. If your "wingman" consistently creates a lot more points than your machine, you should consider moving to a different project.

If you cut off your WU at, e.g. 10% work done after 6 hours, the other computer might have been much more powerful and finished the entire thing. But in the end, only your 10% will be validated and al the rest seht out as another WU. The wingman's 90% will be lost.

Regards,
Martin
----------------------------------------

[May 11, 2010 1:27:14 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: I'm wondering ...

sgoll,

plz ignore that comment by martin64. WCG tries to match devices of same speed as much as possible for this project so that they turn in a fairly equal number of positions packaged in a task. Tries, because tasks can only stay for a limited time in the shared memory after which any wingman that asks for work will get the second task in a quorum.

As noted by Snow Crash, if your jobs manage to get past the first 6 hours it means your device did more than 60% at that turn and will then continue to the finish or until 12 hours have passed. Moreover, HCMD2 is an extremely light task, on memory and on disk, so it's ideal for older / slower devices.

cheers

edit: On the below quoted question, no there is no way around. The soft and hard caps are 6 respectively 12 hours.
So ... if there is a runtime limit on the CMD2 workunits, how can I get around this limit? Or should I disable the complete support für CMD2 only because I user a cruncher that is a bit slow?
Stephan

----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at May 11, 2010 3:06:00 PM]
[May 11, 2010 1:50:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
martin64
Senior Cruncher
Germany
Joined: May 11, 2009
Post Count: 445
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: I'm wondering ...

WCG tries to match devices of same speed as much as possible

Sek, that's what I wanted to say: Have a look at the results, and if the 2 results are fairly equal in average, everything is fine. If - and only if - it consistently had a huge difference, we should discuss your recommendation. smile

Regards,
Martin
----------------------------------------

[May 11, 2010 2:47:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sgoll
Advanced Cruncher
Joined: Oct 24, 2006
Post Count: 87
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: I'm wondering ...

Okay,
the current situation looks like this: my slow crunchers are getting credits ... (not the full credits, but a fair share) und my wingman is getting all the credit for the completed WU. So there is no need to quit (H)CMD2 and I'm happy to contribute to the project.
Thanks for the answers.
Stephan
----------------------------------------

[May 18, 2010 1:50:11 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread