Forum > GPU crunching

CPU <-> GPU rebranding

<< < (71/75) > >>

RottenMutt:

--- Quote from: arkayn on 06 Oct 2010, 01:06:33 pm ---
--- Quote from: Franz on 06 Oct 2010, 12:56:19 pm ---2) reschedule 1.9 (what else?)

--- End quote ---

Fred's rescheduler is better.
http://www.efmer.eu/forum_tt/index.php?topic=428.0

--- End quote ---

so how can i move units to be a ratio of the total to gpu and cpu like in reschedule.exe??

Miep:

--- Quote from: RottenMutt on 28 Dec 2010, 10:29:48 am ---so how can i move units to be a ratio of the total to gpu and cpu like in reschedule.exe??


--- End quote ---

Works by absolute and not relative figures - so not currently possible to give it % . You could ask Fred to add that?

But as Marius' 1.9 Rescheduler doesn't work with x32f...

msattler:
I agree....
The simple slider setting of % to allocate between the CPU and GPU was a convenient way to do it.

Geek@Play:
The Seti servers try to figure out how long a wu will take on the assigned hardware and software and assign that time limit to the wu.  If you then reschedule the task are you not inviting the dreaded -177 errors?  Not to mention the flops values that the servers work out for your client computers is then all messed up.

For these reasons I have stopped using the reschedule tool and have not had a -177 error since before the major failure.  And the flops values that Seti have are very accurate and in my  app_info file.

No problems since not using the reschedule tool.

I should add......I rum MB on my GPU's only and AP on the CPU's.

msattler:
Fred's rescheduling tool fixes the WUs to avoid the -177s.......

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version