Forum > GPU crunching
CPU <-> GPU rebranding
Geek@Play:
Have no idea what Reschedule.elf is but Reschedule created it today. Attached for your inspecion.
[attachment deleted by admin]
Marius:
--- Quote from: Geek@Play on 11 Jul 2009, 02:14:01 pm ---Have no idea what Reschedule.elf is but Reschedule created it today. Attached for your inspecion.
--- End quote ---
Its just a text file containing information about the failure. Unfortunateley i could not extract the exact reason why it was unable to stop the boinc service. It could be because of the 5 seconds timeout i used, 5 sec could be a bit too tight and i extended this to 15 sec.
Raistmer:
Better make this timeout value adjustable (with default of 15 sec or whatever you want). With high-performance hosts each idle second counts ;D
Marius:
--- Quote from: Raistmer on 12 Jul 2009, 07:03:56 am ---Better make this timeout value adjustable (with default of 15 sec or whatever you want). With high-performance hosts each idle second counts ;D
--- End quote ---
lol, if it cant stop boinc under 15 seconds the host doesn't deserve to be running boinc ;)
Raistmer:
--- Quote from: Marius on 12 Jul 2009, 07:39:00 am ---
--- Quote from: Raistmer on 12 Jul 2009, 07:03:56 am ---Better make this timeout value adjustable (with default of 15 sec or whatever you want). With high-performance hosts each idle second counts ;D
--- End quote ---
lol, if it cant stop boinc under 15 seconds the host doesn't deserve to be running boinc ;)
--- End quote ---
I meant something exactly different:
If it will await 15 seconds when BOINC could be stopped for one second - 14 seconds are lost for processing ;)
I'm using now your 1.8 rebranding tool (in manual mode for now) on my x64 host.
One time it complained about can't stop BOINC service (so some adjustments in this area really needed to be done) (but before it could stop it and start again).
But basic functionality works just fine + additional bonus of work balancing between CPU/GPU is just great (especially in times there was no new wrok from servers and CUDA queue completely dry).
Thank you for such nice looking and very useful tool!
IMHO it should be required tool on any CUDA enabled SETI host now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version