Transfer WU to different computer

kratz
kratz
Joined: 9 Sep 05
Posts: 2
Credit: 2561106
RAC: 0
Topic 189911

Does anyone know if you can take a WU from one computer and move it to another? I have an old computer i was just using E@H as a system test, but it is really slow, something like 200 hours per WU, so I want to move the WU to my other computer. I have tried moving the WU file (or what I think it is) from the project folder to thumb drive to new computer's project folder, but it does not show up in boinc manager. I run xpsp2. Thanks

Desti
Desti
Joined: 20 Aug 05
Posts: 117
Credit: 23762214
RAC: 0

Transfer WU to different computer

You might copy the complete BOINC dir, only copying the workunits will not work.

Pooh Bear 27
Pooh Bear 27
Joined: 20 Mar 05
Posts: 1376
Credit: 20312671
RAC: 0

The machine that receives the

The machine that receives the result needs to return the result, or else it will be invalid. So, in short the answer is no you can not move results to a different machine to crunch. There is some elaborate way you can, but then you need to move it back to get it to work, and it is a lot of hassle and programming skills.

Winkle
Winkle
Joined: 24 Aug 05
Posts: 8
Credit: 47604
RAC: 0

RE: Does anyone know if you

Quote:
Does anyone know if you can take a WU from one computer and move it to another? I have an old computer i was just using E@H as a system test, but it is really slow, something like 200 hours per WU, so I want to move the WU to my other computer. I have tried moving the WU file (or what I think it is) from the project folder to thumb drive to new computer's project folder, but it does not show up in boinc manager. I run xpsp2. Thanks

You can try this....
Disable BOINC network access on the slow machine, and set it to NO NEW WORK.
Move the BOINC folder on the fast machine to a safe spot so you can move it back later.
Move the entire BOINC folder (and subfolders) from the slow machine to the fast one. It contains all the info which identifies the computer as well.
BOINC network access will now be disabled on the faster machine with no new work set.
After the work unit has been crunched, move the directory back to the slow machine.
Start BOINC on the slow machine, and force it to do a benchmark. Reenable network access and the WU should be returned.
Restore the original BOINC to the faster machine.
The problem now occurs that you still may not get credit for it depending on just how much work was done on the faster machine. If there is too much discrepancy between what it should have taken and what it did, it may be seen as invalid. I don't know if the benchmarks are taken into account in validation.

I am in a similar position with one of my units about to run into the red (on a P2 400). I am going to try it tonight.

Ziran
Ziran
Joined: 26 Nov 04
Posts: 194
Credit: 615123
RAC: 1329

This is an interesting

This is an interesting question. If you move the whole BOINC folder, you also move the host identity. So the same host number that downloaded the work will also upload it. What you are doing is therefore to be to compared with an upgrade of your host, a big upgrade. But big upgrades are only the sum of small upgrades. Then certain upgrades are done the BOINC client decides it want a new host number. The question therefore becomes how BOINC handles work on a host that have decided it would like a new host number.

Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.