Hey Everyone,

I just tried turning on some options to reduce workunits sent to hosts that return a significant number of errors. If you see any issues, please let me know.

Thank you all for your continued support.

Jake

Hey Everyone,

I just tried turning on some options to reduce workunits sent to hosts that return a significant number of errors. If you see any issues, please let me know.

Thank you all for your continued support.

Jake

Thank you very much, hopefully the credits will flow more quickly now.

I just tried turning on some options to reduce workunits sent to hosts that return a significant number of errors. If you see any issues, please let me know...

Unfortunately, host 643627 went through another cycle this morning of returning 80 errored tasks and getting 80 new tasks. Even though the host has a history of returning a lot of errors, does it take time for the server to "learn" that it's unreliable?

---

Unfortunately, host 643627 went through another cycle this morning of returning 80 errored tasks and getting 80 new tasks...

And it continues...

---

Unfortunately, host 643627 went through another cycle this morning of returning 80 errored tasks and getting 80 new tasks...

And it continues...

What's strange is they have 2 pc's, one works and one doesn't at all, it's got the 2 second error problem.

Another otherwise likely valid result of mine invalidated due to unreliable wingmen (628802 and 761112).

---

Hey Everyone,

I wanted to give this a couple days to see if the server just had to learn who was unreliable. Seems that's not the case. I will do a little more research into configuring the server better throughout the week and run some more tests.

Jake

One of my PCs is not getting any credit for HOST AVERAGE work done, another seems to be working OK. The OK one also posts USER AVERAGE totals which seem to include activity of BOTH of my Milkyway machines as well as what looks like correct HOST AVERAGE totals.

One of my PCs is not getting any credit for HOST AVERAGE work done, another seems to be working OK. The OK one also posts USER AVERAGE totals which seem to include activity of BOTH of my Milkyway machines as well as what looks like correct HOST AVERAGE totals.

Just so there's no confusion, what does this have to do with unreliable hosts? For your hosts, I see some user aborts and errors in N-body tasks. However, no massive and continuing computation errors like those pointed out earlier in this thread.

---

I will do a little more research into configuring the server better throughout the week and run some more tests...

Any update on this, Jake? I've had another result invalidated due to unreliable wingmen. I guess it doesn't make any difference, but all the hosts I've looked appear to be using GPUs that aren't double precision.

---

Nothing new to report yet. I've tried changing a few things on the server config side, but none of it seems to make a difference. Hopefully I will find the right knob to tweak soon.

Jake

I will do a little more research into configuring the server better throughout the week and run some more tests...

Any update on this, Jake? I've had another result invalidated due to unreliable wingmen. I guess it doesn't make any difference, but all the hosts I've looked appear to be using GPUs that aren't double precision.

Maybe they could blacklist some then? Not the actual host but the model of gpu that can't do double precision. That should mean the host can't get work. Another project I crunch for bans any gpu with less than 2gb of ram, I realize that may be a bit easier but it's a start.

Hi Jake,
While you're at it can you find out whats causing the database to crash every now and then?

---

Regards,
Cliff.
--
Been there Done That, still no Damn T-Shirt

Hey everyone,

I found a small bug in the way that the scheduler tests for reliability on workunits with priority 0. I am going to try changing everything to priority 1 and see if that fixes things. Hopefully this won't change how quickly our workunits are processed or affect how it interacts with workunits from other projects. Let me know if you see any issues with this on your end.

Jake

Hey everyone,

I found a small bug in the way that the scheduler tests for reliability on workunits with priority 0. I am going to try changing everything to priority 1 and see if that fixes things. Hopefully this won't change how quickly our workunits are processed or affect how it interacts with workunits from other projects. Let me know if you see any issues with this on your end.

Jake

Thanks I hope that helps!

In the meantime maybe you can see if the pc is affected by it:
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=763376

It got 128 tasks and trashed them ALL!!

Says you have zero workunits in progress. That's a good sign!

Jake

All timeouts. That could have just been a failed hard drive or a PC that was turned off. The ones that have computational errors are the problem clients.

Hey Everyone,

I've done a little digging to see if unreliable hosts are getting fewer workunits now and that does seem to be the case. I have found several faulty computers who currently have 0 work units in progress where they had 100+ plus as of last week.

I am going to consider this issue resolved for now unless anyone objects.

Jake

I am going to consider this issue resolved for now unless anyone objects...

It definitely looks like we're making progress. I'd say we're good to go if 643627 doesn't get new work after it reports its latest batch sometime after 1800 UTC.

I'd say we're good to go if 643627 doesn't get new work after it reports its latest batch sometime after 1800 UTC.

Well, it's still being sent new work in spite of a 100% error rate. However, it's getting fewer and fewer new tasks so maybe it will be completely shut down in another couple of days.

Good work, Jake. Thanks for chasing that down for us.