Forum > GPU crunching
CPU <-> GPU rebranding
Marius:
--- Quote from: Geek@Play on 22 Jun 2009, 01:32:03 am ---Ran Schedule 1.6 with a 50/50 split set in. Seems it took the 4 work units already in progress on the CPU's and rebranded them to CUDA and when Boinc restarted new work units were started. Leaving the newly created CUDA in paused mode. Didn't expect that! Would have been better to leave work already started alone.
--- End quote ---
Yes this is the current behaviour and it indeed leads to a lot of slots. And it will take some time before the stopped units will be restarted again. This is one of the reasons i rather use only the OnlyVLar option (unless CPU/GPU is serious unbalanced or berkeley is down).
And you can take this a step further and workout (with for example a 50% reschedule) a better workload distribution based on current deadlines. For example pushing cpu units to gpu just to lighten the workload stress on cpu side or the other way around. This is something to look at after a proper repear of windowss 64 ;)
Greetings,
Marius
Geek@Play:
Ok, thanks Marius.
Will use the option to rebrand OnlyVLar from now on.
Raistmer:
VLAR+VHAR rebranding could give better performance.
glennaxl:
v1.7 and v1.5 doesnt work with x64
what is written from GPU to CPU:
windows_intelx86 to windows_intelx86
v1.3 works with x64
what is written from GPU to CPU:
windows_intelx86 to windows_x86_64
suggestion:
When it reads the client state file, platform should be placed into a variable.
CPU can be windows_intelx86 and windows_x86_64
GPU for now is only windows_intelx86
Marius:
--- Quote from: Raistmer on 22 Jun 2009, 04:48:22 pm ---VLAR+VHAR rebranding could give better performance.
--- End quote ---
Yes it really does in the case of just vlar/vhar rebranding (but i guess people just hate to go to the trouble of installing the additional perl binaries)
--- Quote from: Geek@Play on 22 Jun 2009, 01:32:03 am ---Seems it took the 4 work units already in progress on the CPU's and rebranded them to CUDA and when Boinc restarted new work units were started. Leaving the newly created CUDA in paused mode.
--- End quote ---
I can detect those and can leave them alone if possible. It just needs additional parsing.
--- Quote from: glennaxl on 24 Jun 2009, 02:53:57 am ---v1.7 and v1.5 doesnt work with x64
v1.3 works with x64
--- End quote ---
AFAIK none of them ever worked on x64 unless the boincmgr (and boinc.exe in the background) is stopped. This is because all versions (should) lock the stdoutdae.txt to make sure boinc isn't running and that changes in client_state.xml wont be corrupted.
I guess what you are suggesting is that i should also change the platform in the results sections while rescheduling because there can be a difference in cpu or gpu application? If thats the ccase thats not a problem. Could you send your client_state.xml so i can see how it looks like (please use winrar or winzip, or use pvt msg).
Greetings,
Marius
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version