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: 121
Posts: 121   Pages: 13   [ Previous Page | 3 4 5 6 7 8 9 10 11 12 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 581649 times and has 120 replies Next Thread
mdparkhill
Advanced Cruncher
Joined: May 2, 2007
Post Count: 60
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT-2 Work Unit distribution updated

Kneed

Where can I find these setting so I can see what mine are?

<reliable_max_error_rate>0.002</reliable_max_error_rate>
<reliable_max_avg_turnaround>172800</reliable_max_avg_turnaround>
<reliable_reduced_delay_bound>0.4</reliable_reduced_delay_bound>
<reliable_on_priority>10</reliable_on_priority>
<reliable_priority_on_over>10</reliable_priority_on_over>

I have found a cc_config.xml in the data directory but it has none of these values in it. Is this something kept in the main servers as our report card of how good or bad we've been???
----------------------------------------

[Mar 10, 2010 4:30:47 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: DDDT-2 Work Unit distribution updated

"Reliable" characteristics are the business of the servers and they are used only by them.

Edit: If I read the first two parameters correctly your device will be considered as "reliable" if it has an average turnaround time of 2 days or less and if it does not error more than once every 500 WUs.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
----------------------------------------
[Edit 1 times, last edit by JmBoullier at Mar 10, 2010 4:54:27 AM]
[Mar 10, 2010 4:48:07 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Ingleside
Veteran Cruncher
Norway
Joined: Nov 19, 2005
Post Count: 974
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT-2 Work Unit distribution updated

"Reliable" characteristics are the business of the servers and they are used only by them.

Edit: If I read the first two parameters correctly your device will be considered as "reliable" if it has an average turnaround time of 2 days or less and if it does not error more than once every 500 WUs.

Yes, and no...
For the average turnaround-time the cut-off is 2 days, yes. For normal BOINC-projects the average turnaround-time is displayed as part of the computer-info on the web-pages, so users can see their current turnaround-time, but WCG is missing this page...

For the host.error_rate on the other hand, new hosts starts at 0.1, and needs 77 validated tasks in a row to drop below 0.002. In case has one task failing validation, you'll need atleast another 77 tasks to become reliable again.

Worse-case scenario, the host.error_rate has become 1 (10 or more validation-errors close together). In this instance you'll need 122 validated tasks in a row to drop below 0.002.
----------------------------------------


"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
[Mar 10, 2010 5:58:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Jack007
Master Cruncher
CANADA
Joined: Feb 25, 2005
Post Count: 1604
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT-2 Work Unit distribution updated

"Reliable" characteristics are the business of the servers and they are used only by them.

Edit: If I read the first two parameters correctly your device will be considered as "reliable" if it has an average turnaround time of 2 days or less and if it does not error more than once every 500 WUs.


Uh oh, when I had virtual mem set to ZERO, I errored out a bunch, I bought 6 more GIGS of RAM (12 total) and set VM to 1-3 gigs, and did 22 more DDDT units (from the first day most of them). I just got a 20 day (which will be done in less than 2 I hope), but will I still be on the 'unreliable' list? Will all the HFCC that I do, having set a 1 day buffer, cause me to come back to the 'fold'?
It's not the end of the world if I dont crunch Dengue right away, I have 6 and a half years of projects to do to get all open projects to BLUE, I just want to be up there crunching all that I can.
----------------------------------------

[Mar 10, 2010 6:10:30 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: DDDT-2 Work Unit distribution updated

Um, the four wu I got this afternoon have a 20-day deadline and a replication of only 2. Once I spotted them I suspended my other WCG work so these can get done soonest, but no idea of the state of my crunching partner.
wus are ts02_a490,491,495,498_ps0000
[Mar 10, 2010 6:41:47 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Ingleside
Veteran Cruncher
Norway
Joined: Nov 19, 2005
Post Count: 974
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT-2 Work Unit distribution updated

Uh oh, when I had virtual mem set to ZERO, I errored out a bunch, I bought 6 more GIGS of RAM (12 total) and set VM to 1-3 gigs, and did 22 more DDDT units (from the first day most of them). I just got a 20 day (which will be done in less than 2 I hope), but will I still be on the 'unreliable' list? Will all the HFCC that I do, having set a 1 day buffer, cause me to come back to the 'fold'?

Well, windows does like it's pagefile...

I don't know how many valid results your computer has done, so can't say if it's currently reliable.

But, it can atleast become "reliable" in the future, as long as all work on computer validates, and your turnaround-time isn't too large.

The turnaround-time shouldn't be a problem with 1-day cache-size, as long as you're not running other BOINC-projects.

And the valid results is just to return enough, worse-case-scenario this is 122 in a row.
----------------------------------------


"I make so many mistakes. But then just think of all the mistakes I don't make, although I might."
[Mar 10, 2010 8:35:04 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Curly2
Cruncher
Joined: Nov 24, 2008
Post Count: 10
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT-2 Work Unit distribution updated

Last night I got 10 wus (20 day deadline, only 1 wu with replication 4). Those are my first DDDT-2 workunits. Never had any before. As the estimated time is only 40% of the real runtime (~48hrs), the dual core is quite overloaded to stay reliable. sad

For the average turnaround-time the cut-off is 2 days, yes. For normal BOINC-projects the average turnaround-time is displayed as part of the computer-info on the web-pages, so users can see their current turnaround-time, but WCG is missing this page...


Also I would like to see the error rate for each host. Then i would know if one host is reliable or to crunch until it is. Til then it's like sitting in the dark.
----------------------------------------

[Mar 10, 2010 9:14:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
rembertw
Senior Cruncher
Belgium
Joined: Nov 21, 2005
Post Count: 275
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: DDDT-2 Work Unit distribution updated

I have 3 of the first release, and those machines will easily handle the 8-day return limit. Should I abort those tasks or let them run?

Personally I'd love to finish them so I get a bit nearer to the badge, but if it's really useless...

Techs? What do you say?
[Mar 10, 2010 9:39:24 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: DDDT-2 Work Unit distribution updated

Last night I got 10 wus (20 day deadline, only 1 wu with replication 4). Those are my first DDDT-2 workunits. Never had any before. As the estimated time is only 40% of the real runtime (~48hrs), the dual core is quite overloaded to stay reliable. sad


That could be a real problem for some peeps.

The few that I have now had an original estimate of 20:22, but it looks like more realistically they will finish around anything from 22+ to 26+ hours.



Should'nt be a problem here with only 11 of them, but I can see how it could be for some.
----------------------------------------
[Edit 1 times, last edit by Former Member at Mar 10, 2010 11:50:15 AM]
[Mar 10, 2010 11:48:17 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: DDDT-2 Work Unit distribution updated

Well I have 11 of those just now and I am just going to abort all of them. NOT !! laughing wink I am reliable BTW. laughing

Well, I'm not so sure you is reliable... tongue

Your computer on the other hand is maybe within the WCG-requirements and can be counted as reliable. cool


laughing laughing :thumbsup:
[Mar 10, 2010 11:52:31 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 121   Pages: 13   [ Previous Page | 3 4 5 6 7 8 9 10 11 12 | Next Page ]
[ Jump to Last Post ]
Post new Thread