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: 12
Posts: 12   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1534 times and has 11 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Server aborted task forces device to unreliable

Hello andzgrid,
It makes me wonder why a logic-flowchart for WCG that shows the factors in determining when/if a computer would be deemed as 'reliable' at WCG -- is not made available.

As of April 2012, knreed said that for a host to be reliable, this is now done at the app_version level. To be reliable a host must have 5 consecutive valid results, be allowed the full daily quota of results for the app_version, and have a average turnaround for the app_version less than 2 days.

In early October knreed said that he had changed the code so that aborts (user or server) did not affect the counter used to determine reliability for an app_version.

I don't know if he has put in more changes or whether any new bugs have been introduced into the server code.

Lawrence
[Nov 17, 2012 2:51:06 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: Server aborted task forces device to unreliable

A flow chart, for those wondering:


In pdf format :
[Nov 17, 2012 4:14:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 12   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread