Wow you must have been sucking them in with 8 and 38 schedule to get Sapphire in less than a month. With your server what was your execution time?

I have more machines available than just the server. Average run time on the server about 20 hours.

Here it says about reliability of hosts: "have at least 10 consecutive valid results are considered 'reliable'". A bit ambiguous, I guess the bit about ten consecutive valid results would probably only pertain to WUs within the same project? Does not seem to mention host aborts done before they even started processing, or from a completely different project.


I was just assuming my rig will ask more frequently for Africa WUs if the other cores are idle. But if my machine only gets one WU every other day I will certainly revert to mixed WUs, otherwise its a waste of resources.


Seems to me the opposite is occurring. Currently says 71% completed, 13:05 elapsed, and only 9:41 to completion.

In my crunching when I want to be selective I suspend pending WU's versus abort it , which works well with due dates of 10 days. I think keeping your machine busy is the way to go (without an excessive Cache) . If the planets align and you get ARP WU you can suspend WU's ahead of the ARP and get crunching since they have shorter due times.

Fingers crossed on the ARP predictions... I sure had some weird S**t occur when crunching my 38. At least 6 WU were stuck at 99% for hours (first one was there for 4 hrs!!!). I restarted my comp and they came up a reduced % and Estimated completion time of 2D 14 hr.. They proceeded on with Cpu time of My average...2D 14Hr

If this does not happen to you after 5 WU , it could be a Windows 10 compatibility issue.

Well, surprise surprise, my trusty old 2012 laptop finished much quicker than the estimate: 16.88hrs (still pending validation though)
https://www.worldcommunitygrid.org/ms/device/....do?workunitId=1376122533

I am wondering if the high amount of ram might have helped.
Or maybe some WUs vary in the amount of work they require