Tansferring WU to new machine?

Message boards : Number crunching : Tansferring WU to new machine?

Author	Message
Russ Sheldon Send message Joined: 18 Jan 01 Posts: 371 Credit: 348,724,485 RAC: 3,417	Message 1133003 - Posted: 28 Jul 2011, 15:39:30 UTC
	What's the best way, very specifically, to transfer un-crunched WU from one machine to another? Thanks, Russ ____________ Now a proud GPU Users Group 10.1 percenter. Yes Tron, all your base are belong to us! Volunteer idiot. ********CAUTION! competitive jerk************
	ID: 1133003 ·

B-Man Volunteer tester Send message Joined: 11 Feb 01 Posts: 253 Credit: 147,366 RAC: 0	Message 1133005 - Posted: 28 Jul 2011, 15:41:43 UTC
	I think BOINC is specifically designed against that. I know you can't easily transfer work between machines. ____________
	ID: 1133005 ·

HAL9000 Volunteer tester Send message Joined: 11 Sep 99 Posts: 3297 Credit: 78,568,689 RAC: 60,714	Message 1133007 - Posted: 28 Jul 2011, 15:43:52 UTC
	The easiest way is probably: 1. Install BOINC on the new machine. 2. Close/exit BOINC on the new machine. 3. Close/exit BOINC on the old machine. 4. Copy the contents of the data folder from the old machine to the new one. Note: The location of your data folder can very depending on the OS. 5. Start BOINC on the new machine. 6. Crunch... Crunch... Crunch... ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today!
	ID: 1133007 ·

Volunteer tester Send message Joined: 9 Apr 02 Posts: 12016 Credit: 19,625,213 RAC: 41,225	Message 1133008 - Posted: 28 Jul 2011, 15:48:46 UTC - in response to Message 1133007.
	The easiest way is probably: 1. Install BOINC on the new machine. 2. Close/exit BOINC on the new machine. 3. Close/exit BOINC on the old machine. 4. Copy the contents of the data folder from the old machine to the new one. Note: The location of your data folder can very depending on the OS. 5. Start BOINC on the new machine. 6. Crunch... Crunch... Crunch... Even easier than that. Since BOINC's uninstaller is non-destructive, you can do it like this: 1. Uninstall BOINC on old machine. This leaves behind the data directory where all workunits are stored. 2. Move data directory to the new machine. 3. Install BOINC on the new machine and make sure the installer points to the correct data directory (if it isn't the default) BOINC will automatically pick up where it left off. Note that if you were using optimized apps, you may want to look into re-installing if your new machine supports a newer/better instruction set.
	ID: 1133008 ·

1mp0£173 Volunteer tester Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0	Message 1133041 - Posted: 28 Jul 2011, 17:13:18 UTC - in response to Message 1133003.
	What's the best way, very specifically, to transfer un-crunched WU from one machine to another? Thanks, Russ You can transfer the identity of a machine to a different machine, including un-crunched work. If you have a slow machine with tons of work, and a fast machine that is empty, you could actually swap identities. What you can't do is take some work on machine "A" and give it to machine "B." One form of widespread cheating in SETI Classic was to have one machine download work, crunch it on multiple machines offline, and then give it back to the original machine to return -- making that original machine seem mind-bogglingly fast.
	ID: 1133041 ·

Russ Sheldon Send message Joined: 18 Jan 01 Posts: 371 Credit: 348,724,485 RAC: 3,417	Message 1133067 - Posted: 28 Jul 2011, 18:25:39 UTC - in response to Message 1133041.
	Thanks for the feedback. Half wrong, half right. Can't get WU's to be used in new directory. BOINC tasks doesn't see them. How do I change the identity? Thanks! ____________ Now a proud GPU Users Group 10.1 percenter. Yes Tron, all your base are belong to us! Volunteer idiot. ********CAUTION! competitive jerk************
	ID: 1133067 ·

BMH Send message Joined: 27 May 99 Posts: 270 Credit: 61,945,064 RAC: 55,085	Message 1133068 - Posted: 28 Jul 2011, 18:25:54 UTC - in response to Message 1133041.
	What's the best way, very specifically, to transfer un-crunched WU from one machine to another? Thanks, Russ You can transfer the identity of a machine to a different machine, including un-crunched work. If you have a slow machine with tons of work, and a fast machine that is empty, you could actually swap identities. What you can't do is take some work on machine "A" and give it to machine "B." One form of widespread cheating in SETI Classic was to have one machine download work, crunch it on multiple machines offline, and then give it back to the original machine to return -- making that original machine seem mind-bogglingly fast. I used to do this, not to cheat but because machine "A" (at work) had internet access and machine "B" (at home) didn't. I never realised it was considered cheating or that anyone was looking at the performance of machine "A". ____________ Brian.
	ID: 1133068 ·

skildude Send message Joined: 4 Oct 00 Posts: 8973 Credit: 37,844,644 RAC: 43,695	Message 1133087 - Posted: 28 Jul 2011, 19:24:34 UTC - in response to Message 1133068.
	sharing WU's is no longer viable since your machine will eventually want to return the work and you can't have 2 machines with the same ID ____________ Proud member of TSWB. End terrorism by building a school
	ID: 1133087 ·

S@NL - John van Gorsel Volunteer tester Send message Joined: 5 Jul 99 Posts: 176 Credit: 121,703,400 RAC: 54,953	Message 1133400 - Posted: 29 Jul 2011, 8:23:36 UTC - in response to Message 1133068. Last modified: 29 Jul 2011, 8:24:05 UTC
	I used to do this, not to cheat but because machine "A" (at work) had internet access and machine "B" (at home) didn't. I never realised it was considered cheating or that anyone was looking at the performance of machine "A". I don't think this was ever considered as cheating. What I can remember is that some people ran a task on one pc up to 99%, than distribute that task to multiple machines and let those machines finish the last % and return the result. And that was cheating... ____________
	ID: 1133400 ·

-BeNt- Send message Joined: 17 Oct 99 Posts: 1234 Credit: 10,116,112 RAC: 0	Message 1133415 - Posted: 29 Jul 2011, 10:08:20 UTC
	Wouldn't the machine just realize it can't use the old WU's an abandon them? You know clientID and all. Maybe if you did the merger clients thing BEFORE you load them up. ____________ Traveling through space at ~67,000mph!
	ID: 1133415 ·

HAL9000 Volunteer tester Send message Joined: 11 Sep 99 Posts: 3297 Credit: 78,568,689 RAC: 60,714	Message 1133445 - Posted: 29 Jul 2011, 12:38:19 UTC - in response to Message 1133067.
	Thanks for the feedback. Half wrong, half right. Can't get WU's to be used in new directory. BOINC tasks doesn't see them. How do I change the identity? Thanks! Depending on what state BOINC is in now you can either do a project detach/attach or just remove BOINC and reinstall it. Then attach to the project. If you still have the data from the old machine intact you might be able to try again. If BOINC aborted the tasks on the new machine then you are out of luck. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today!
	ID: 1133445 ·

Message boards : Number crunching : Tansferring WU to new machine?