Forum > GPU crunching
CPU <-> GPU rebranding
Marius:
--- Quote from: Raistmer on 12 Jul 2009, 09:48:02 am ---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 ;)
--- End quote ---
Speaking about junks talking about 10 whole seconds lost :o
--- Quote from: Raistmer on 12 Jul 2009, 09:48:02 am ---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.
--- End quote ---
Hey thanks man, remember its basicly your tool as i just took your excellent idea and extended it a little bit (basicly i picked it up because my queue went dry back then)
This reminds me that i actually forgot to publish the 1.9
1.9 changes:
-Now display's the amount of VLAR and VHAR
-Changed the parsing of client_state.xml so seti@home beta can be run also
-Automatic detection of the right seti_enhanced applications so this tool
can also work with future versions of the seti applications.
-VHAR is now only optionally rescheduled to the CPU (see settings)
-Alternative detection of VLAR/VHAR (True Angle Rate) has been removed.
-->Also noticed 2 little problems:
-Noticed tool does not automaticly pickup seti paths under vista (security problem)
-Noticed tool crashes when browsing for data path under vista (please enter the path manually)
Enjoy,
Marius
[attachment deleted by admin]
Samuel:
--- Quote from: Marius on 12 Jul 2009, 10:20:30 am ---This reminds me that i actually forgot to publish the 1.9
--- End quote ---
Thanks for the new version.
I haven't run it yet as I just ran Raistmer's script but on the settings tab the first option is still 'Only VLAR+VHAR to CPU.' I suppose this is just a cosmetic leftover and the functionality has changed.
Do I understand correctly that the tasks already being crunched are excluded from the figures? If so, the test function returned correct figures.
On my Vista64, the paths were picked up automatically and I was able to browse for the data path.
Raistmer:
--- Quote from: samuel7 on 12 Jul 2009, 11:00:23 am ---
--- Quote from: Marius on 12 Jul 2009, 10:20:30 am ---This reminds me that i actually forgot to publish the 1.9
--- End quote ---
on the settings tab the first option is still 'Only VLAR+VHAR to CPU.' I suppose this is just a cosmetic leftover and the functionality has changed.
--- End quote ---
I noticed that too and perceive it as "not touch usual tasks and not do % rebranding"
Cause VLAR and VHAR now counted separately (good idea actually) it's very easy to check.
Marius:
--- Quote from: samuel7 on 12 Jul 2009, 11:00:23 am ---I haven't run it yet as I just ran Raistmer's script but on the settings tab the first option is still 'Only VLAR+VHAR to CPU.' I suppose this is just a cosmetic leftover and the functionality has changed.
--- End quote ---
Yes small leftover, the first checkbox locks out the percentage (it grays some controls also to reflect that) and the second checkbox controls if the vhar are pushed back to the cpu.
--- Quote from: samuel7 on 12 Jul 2009, 11:00:23 am ---Do I understand correctly that the tasks already being crunched are excluded from the figures? If so, the test function returned correct figures.
--- End quote ---
Yes, the currently running units are always excluded because i can't switch the applications of those because that info has already been entered into the slot directory (previous versions did reschedule those, but i doubt if that had any effect).
--- Quote from: samuel7 on 12 Jul 2009, 11:00:23 am ---On my Vista64, the paths were picked up automatically and I was able to browse for the data path.
--- End quote ---
Thats good to hear, here with a unpatched vista 64 under virtualbox it just refuses (even when it was run as adminisrator).
Thanks for reporting back,
Marius
Geek@Play:
I feel I must echo Raistmer's comments..........
Thank you for such nice looking and very useful tool!
IMHO it should be required tool on any CUDA enabled SETI host now.
Thank You
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version