somethingsketchy
Golden Member
64 moar cores crunching as of right now 😉
Yah!
64 moar cores crunching as of right now 😉
I've already shut down any receipt of new tasks and plan on burning through the queue that I have (roughly 10 tasks). I've also up'd the number of threads on the main rig to hopefully burn through those tasks.
True. There is a configuration setting to flush immediately when a WU finishes, but I can't find it right now.If you do not allow new tasks you may have to manually flush before the end of the race or is there a way to avoid this?
True. There is a configuration setting to flush immediately when a WU finishes, but I can't find it right now.
Another option is to judge when a machine has downloaded all the work it's going to complete for the race, and then switch it to a "location" (home, work, school, or (none)), running something fast like PPS LLR. It should then download that work frequently, and upload your results at the same time.
Edit: My shell script, in the same thread with my juggling guide, will flush for you if you're on Linux.
So, they need to be reported in before the race concludes, is that it?
This is pretty much what I am doing. I am betting that I already have enough WUs to complete the competition on time.
That's correct, all WUs need to be done on time, in order to be counted for the competition.
I guess I assumed they had some sort of completion time stamp on them - but I suppose there would be those that cheat at even something like this.
FYI, older machines like Core 2 Quads are bottlenecked in their RAM bandwidth. If 4 WUs aren't going to finish in time, abort 2 or 3.