Forum > GPU crunching
CPU <-> GPU rebranding
Richard Haselgrove:
--- Quote from: MarkJ on 04 Jul 2009, 07:51:49 am ---
I did notice that the rebranded work units immediately went into "running, High Priority" mode. Seems their estimated time was 20+ hours. That estimate is dropping like a stone as it starts crunching them so it will work it out, but they will be finished by the time the TSI has come up (60 mins).
--- End quote ---
If tasks are estimated at 20 hours, but finishing in less than 1 hour, you have a horribly out-of-kilter Duration Correction Factor. With no VLAR handler in place, I would have expected a sawtooth waveform with maybe a factor of 4x between peak and valley, but 20x? ??? No wonder you were seeing preemptions and EDF on boinc_alpha.
I suggest a sanity-check on the FLOPs estimates in your app_info: once the after-effects of your CUDA/VLAR processing have worked their way out of your system, estimates for all SETI work (MB/CPU, MB/CUDA, and AP) should be accurate within a few %.
Marius:
--- Quote from: Richard Haselgrove on 04 Jul 2009, 07:33:05 am ---How are the CPU and CUDA versions defined in your application? Are they hard-coded version numbers, or are they data picked up from the .ini file? It would be better, in the long run, to use configuration data to establish the version numbers, to allow for future Berkeley releases and special cases like Morten's.
--- End quote ---
At the moment they have been hardcoded (just 2 references), but it isn't a lot of work making them configurable.
I think its even better to just figure out the right applications from the client_state.xml. Take a look at the /client_state/app_version/. Filter those on app_name=setiathome_enhanced, if i'm right (not really sure) there are alway's two applications for setiathome_enhanced with one marked with a plan_class=cuda (at the moment 603 and 608/cuda).
I need the platform info from the application section anywhay as i need to brand the platform as well (as Glennaxl asked a while back), picking up the version numbers would just be a perfect way to get the tool working for future versions of MB.
Greetings,
Marius
Richard Haselgrove:
Good thinking!
Edit - during transitional periods, there may be more than one version number in there for any one plan_class - some old work downloaded and still scheduled to be crunched with an older version, and some new work with references to a new version. Best BOINC practice would be to scan the versions, and choose the highest available for the app/plan/platform.
Marius:
--- Quote from: MarkJ on 04 Jul 2009, 07:51:49 am ---One question about the automatic mode and the default time of 4 hours. I assume it just sits there waiting for the 4 hours to be up and then does its scan/rebrand before going back to sleep. I don't need to get windows to schedule it?
--- End quote ---
Yes, its just a idle background application waiting for the 4 hours timeout (or whatever hours you have configured it to run). It does all the work itself without the need for the standard windows scheduler (or other complicated stuff).
However if you want it to work from within batch files or via windows scheduler use the commandline "Reschedule.exe /Autorun <percentage>". It will start, do its thing and exit immediately.
Greetings,
Marius
Marius:
--- Quote from: Richard Haselgrove on 04 Jul 2009, 08:26:54 am ---Good thinking!
Edit - during transitional periods, there may be more than one version number in there for any one plan_class - some old work downloaded and still scheduled to be crunched with an older version, and some new work with references to a new version. Best BOINC practice would be to scan the versions, and choose the highest available for the app/plan/platform.
--- End quote ---
Excellent idea!
The "old" units would have been already rescheduled anywhay so very little chance on V*AR in the old cuda application.
Greetings,
Marius
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version