That allows us to delete the file from our local disks sooner than we otherwise would and keep our splitters generating data files at a high rate. There has to be more than one way to get by all these .427AR . That allows us to delete the file from our local disks sooner than we otherwise would and keep our splitters generating data files at a high rate. The likelihood is that one of the other multiple copies of any given WU is going to be processed and returned by someone else, before the WU works its way to the top of your queue. It seems to me that those who cache will almost always be crunching WUs that have already been returned by someone else.
Time is nature's way to keep everything from happening all at once.
The thing is, when they distribute it multiple times, it compares the results, so it makes sure that the client hasn't been hacked. Seti needs to have at least 2 returned WUs for each piece of sky. In addition to checking for hacked clients, there are other, normal ways a WU gets corrupted. There needs to corroborative evidence for each piece of sky. The likelihood is that one of the other multiple copies of any given WU is going to be processed and returned by someone else, before the WU works its way to the top of your queue.