Forum > GPU crunching
CPU <-> GPU rebranding
BANZAI56:
Am I the only one having trouble downloading this?
Can't get 1.7 or 1.8..says IE can't d/l from site...
Any other link to it available?
Marius:
--- Quote from: samuel7 on 05 Jul 2009, 11:29:36 am ---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.
--- End quote ---
Internally i know exactly those groups, but if you are using Raistmer's MB_6.08_mod_CUDA_V11_VLARKill_refined.exe al vhar's will be automaticly killed AFAIK (true angle rate > 1.127), so i assume you are running a different tool what can handle a VHAR?
Or i'm i wrong here? (i use Raistmer's tool for several years now and don't even know what the original tools are any more)
Richard Haselgrove:
There's no actual need to rebrand VHAR. They run adequately on the GPU, and they don't cause any screen stuttering or other computer-use problems. Raistmer has just observed a slight efficiency gain (i.e. optimisation) by using the CPU instead of the GPU for VHAR, but it's not enough to lose any sleep over. In any case, much of the efficiency gain is lost on Quads and above when there are lots of VHAR about, because they suffer from memory bus contention.
VLAR are different entirely. Their efficiency on GPU is abysmal, and the general screen delay makes the rest of the computer unusable - it's driven away many potential crunchers. Anything you can do to keep them off the GPU is a big step forward - but I prefer rebranding to killing.
Samuel:
--- Quote from: Marius on 05 Jul 2009, 11:48:41 am ---
--- Quote from: samuel7 on 05 Jul 2009, 11:29:36 am ---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.
--- End quote ---
Internally i know exactly those groups, but if you are using Raistmer's MB_6.08_mod_CUDA_V11_VLARKill_refined.exe al vhar's will be automaticly killed AFAIK (true angle rate > 1.127), so i assume you are running a different tool what can handle a VHAR?
Or i'm i wrong here? (i use Raistmer's tool for several years now and don't even know what the original tools are any more)
--- End quote ---
No no no, VHAR runs fine with all Raistmer's apps. Only VLARs are killed (by apps so named). Discussion here
Edit - Richard beat me to it
Marius:
--- Quote from: Richard Haselgrove on 05 Jul 2009, 12:00:54 pm ---There's no actual need to rebrand VHAR. They run adequately on the GPU, and they don't cause any screen stuttering or other computer-use problems. Raistmer has just observed a slight efficiency gain (i.e. optimisation) by using the CPU instead of the GPU for VHAR, but it's not enough to lose any sleep over. In any case, much of the efficiency gain is lost on Quads and above when there are lots of VHAR about, because they suffer from memory bus contention.
VLAR are different entirely. Their efficiency on GPU is abysmal, and the general screen delay makes the rest of the computer unusable - it's driven away many potential crunchers. Anything you can do to keep them off the GPU is a big step forward - but I prefer rebranding to killing.
--- End quote ---
Thanks for clearing this up, this could/will save lots of rebranding compared to the current version. And thank you samuel7 for reminding me about it! (so logical when you hear it afterwards :()
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version