Forum > GPU crunching

CPU <-> GPU rebranding

<< < (32/75) > >>

Geek@Play:
This config...........

[Settings]
Position=50
OnlyVLarVHar=0
TrueAngleRate=0
DataPath=D:\BOINC\
BoincBinPath=C:\Program Files\BOINC\

[Automatic]
Automatic=0
Interval=4
CPUPerInterval=50
GPUPerInterval=150

Resulted with this.........

---------------------------
Reschedule version 1.8
Time: 05-07-2009 09:22:59
User forcing a reschedule

Stopping BOINC service
BOINC service is stopped
CPU tasks: 255 (255 VLAR/VHAR)
GPU tasks: 230 (215 VLAR/VHAR)
Boinc applications
setiathome_enhanced 603 windows_intelx86
setiathome_enhanced 608 windows_intelx86 cuda
After reschedule:
CPU tasks: 470 (470 VLAR/VHAR)
GPU tasks: 15 (0 VLAR/VHAR)
Starting BOINC service
BOINC service started

and I'm trying to get a 50-50 split on the work units.
All this is run from a batch file with this commmand.........

ReSchedule.exe /Autorun 50

Marius:

--- Quote from: Geek@Play on 05 Jul 2009, 10:39:27 am ---CPU tasks: 470 (470 VLAR/VHAR)
GPU tasks: 15 (0 VLAR/VHAR)
Starting BOINC service
BOINC service started

and I'm trying to get a 50-50 split on the work units.
All this is run from a batch file with this commmand.........

--- End quote ---
Yes, didn't i tell you you would see an akward rise in V*AR :o. V*AR are always forced on the cpu no matter what happends to avoid vlarkill, then as a bonus it tries to confirm to the 50% rule but it cannot do this unfortunately.

Compare your's with mine. i have over 1k of f<beep> V*AR! (9 day's queue)
CPU tasks: 1035 (1035 VLAR/VHAR)
GPU tasks: 942 (0 VLAR/VHAR)
The numbers of V*ar are so bad lately i just reschedule with 100% to gpu.

Geek@Play:
OK.....thanks for the explanation.

Marius:

--- Quote from: Geek@Play on 05 Jul 2009, 11:03:00 am ---OK.....thanks for the explanation.

If you reschedule 100% to GPU does that not leave the CPU's cold??

--- End quote ---
Yes, normally it would, but with the current overflow of VLAR/VHAR units i push every unit to cuda that becomes available (and isn't v*ar), this keeps my cuda going for the moment.

Samuel:

--- Quote from: Marius on 05 Jul 2009, 10:54:21 am ---Yes, didn't i tell you you would see an akward rise in V*AR :o. V*AR are always forced on the cpu no matter what happends to avoid vlarkill, then as a bonus it tries to confirm to the 50% rule but it cannot do this unfortunately.

--- End quote ---

Suggestions for future versions:
Perhaps only VLAR should be forced to CPU. Allow VHAR to go either way, default to CPU however. Maybe the test function could show the task counts by AR group (VLAR/VHAR/other) before and after with current settings.

Thanks again for your work.

Navigation

[0] Message Index

[#] Next page

[*] Previous page