Forum > GPU crunching

Short results reshedule for CPU

<< < (2/2)

Raistmer:

--- Quote from: Pepi on 06 Feb 2010, 01:44:17 pm ---In that case I am very confused!!!!  ::)
Reschedule tools shows only 105 VHARS  and I have got 240 task with short times. ( all times are same cca 7 minutes)


--- End quote ---

That is, VHAR threshold used in Re-schedule just differs from threshold used to estimate running time.
What strange in that? If you would see let say 200 VHARs and only 100 "short" tasks - that would sound strange to me ;)

Pepi:

--- Quote from: Raistmer on 06 Feb 2010, 01:50:42 pm ---
--- Quote from: Pepi on 06 Feb 2010, 01:44:17 pm ---In that case I am very confused!!!!  ::)
Reschedule tools shows only 105 VHARS  and I have got 240 task with short times. ( all times are same cca 7 minutes)

[/qote]

That is, VHAR threshold used in Re-schedule just differs from threshold used to estimate running time.
What strange in that? If you would see let say 200 VHARs and only 100 "short" tasks - that would sound strange to me ;)


--- End quote ---

That option I would love to have :)
To determine only short ones between VHARS
--- End quote ---

Raistmer:
Again, ALL VHARs are short. Reverse isn't true, not all shorties are VHARs.
If AR of task near VHAR threshold it will have small execution time too, but will be not VHAR from re-scheduler point of view.
You could adopt my perl script to move short tasks to CPU if you want.

Pepi:
Perl script never work for me ( win 7 64 bit) so I left that script and wait fro CPU2GPU tools :)
But thanks for answer, maybe I came back to script

Navigation

[0] Message Index

[*] Previous page