Forum > GPU crunching
CPU <-> GPU rebranding
hiamps:
I had to abort some CPU Vlars a couple months ago or so but since then the reschedurer has done a pretty good job. A couple get thru but I do try and run every unit, so far am lucky my CPU units seem to stay just in reach of completion. I have been running a 7 day cache for about 2 months now.
WinyterKnight:
--- Quote from: Fredericx51 on 05 Apr 2010, 12:17:01 pm ---It works beautifull, only my X64 host, has sometimes, troubles, lost connection to local host, connecting. . . . .
REVerting to 'older'Drivers, 190.38 & 190.61 put an end to this and 'oher' UNexplained error's, which appeared to be heat problems and 'flat' the 'tower' , :olayed it on it's side
Even on VISTA Home Premium 32BIT, it works
And when I see 1 host with only CUDA and VHAR, then those are partly REbranded again for CPU.
--- End quote ---
I had similar problem a few years ago. It turned out that gravity was stronger than the heatsink mounts. Bought a new heatsink with better mounting brackets.
mr.mac52:
For what it's worth, in 6 months of using the rebranding tool and not killing VLARs, I've only had one instance of a VLAR get to my GPU. I did upgrade my GPU to a 285 from an 8800 which does speed up CUDA units but the hourly running of Marius's tool seems to keep me running full out as long as there are work units to crunch.
efmer (fred):
A new rescheduling tool:
http://www.efmer.eu/forum_tt/index.php?topic=432.0
I try to actively maintain the project, so requests are welcome.
Frizz:
I tested ReSchedule1.9 on one of my hosts: An ION based HTPC (Intel Atom CPU + NVIDIA 8400M GPU).
Lots of WUs stopped with errors - this didn't happen before.
Questions:
1) Are SETI GPU tasks different from SETI CPU tasks (smaller, need less memory, etc.) ?
2) The GPU on my ION has 512MB (shared memory). Might this be the problem?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version