Forum > GPU crunching
CPU <-> GPU rebranding
Marius:
No problem KarVi, i added a commandline param. When started you only see the process in the taskmanager as its a GUI application.
For pushing 75% of the units to the GPU use:
ReSchedule.exe /Autorun 75
Enjoy,
Marius
[attachment deleted by admin]
Jason G:
Cool, I've also set this up on one of my machines in scheduled tasks to run once every three hours, using a batch file that stops boinc service first, then restarts it. Seems to be working. Nice one ;D
Marius:
--- Quote from: Jason G on 01 Jun 2009, 12:45:00 pm ---every three hours
--- End quote ---
In my experience each time you stop boinc service you will loose a (big) part of the workunits in process (unless you only run GPU). I guess executing it once every 24 or 48 hours would be fine to deal with the vlar/vhar problems.
KarVi:
Thanks Marius for the swift developement of a new version.
Will set this up to run once every 24 hours, and see how things develop.
Thanks again, this will make things easier going ahead.
Richard Haselgrove:
--- Quote from: Marius on 01 Jun 2009, 04:55:02 pm ---
In my experience each time you stop boinc service you will loose a (big) part of the workunits in process (unless you only run GPU). I guess executing it once every 24 or 48 hours would be fine to deal with the vlar/vhar problems.
--- End quote ---
Then you have something wrong with your setup. I've lost about three or four tasks, in total, over several machines and several years. Unfortunately, most of them were CPDN tasks!
One set of problems was related to a failing hard disk (accepted for replacement under RMA) - BOINC apps couldn't read back their checkpoint files on restart.
Another cause is the <platform> tag which I erroneously put in early versions of the CUDA app_info.xml - if you still have that, it should come out.
I run a script which checks first to see how many VLAR tasks (and optionally VHAR tasks) are in the CUDA queue, and how close they are to the head of that queue. If nothing nasty is likely to happen in the near future, it doesn't bother with the stop/restart cycle - so I can run it as often as I like (every 6 hours seems plenty). Maybe you could think about something like that?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version