Forum > GPU crunching
x38g reports
Jason G:
--- Quote from: perryjay on 12 Jul 2011, 09:05:35 am ---FYI, I picked up and ran an AP on my GPU last night. That could have been the problem. Everything is back up to speed after rebooting but my MB tasks on GPU are running high priority. That should settle down after a couple run here soon. I also have a few APs waiting so we shall see what happens.
--- End quote ---
Something to watch: I have no idea if Raistmer included any boincApi fixes for modern Cuda 4.0 drivers, or if they'd be needed under OpenCL running as they most definitely are under Cuda. One way to find out would be to repeatedly exit Boinc (shutting down the AP while in progress) [or just snooze/unsnooze etc) & see if it triggers a sticky downclock or not. If so, then you'll just have to slap Raistmer around a bit to fix it. [ I mean ask nicely... :D]
Jason
perryjay:
I'm over in his thread too. Seems it tried to start two APs at once a bit ago. After 10 minutes I had to suspend the second one as it hadn't even started yet. It was strange because even though I changed the count to .5 I had not changed the number of iterations. The only thing I can think of is the fact it was guesstimating the TTC as over 1600 hours and it just over rid everything else. Once I finish this first AP things should drop drastically and I will see what happens.
Claggy:
--- Quote from: Jason G on 12 Jul 2011, 11:48:50 am ---
--- Quote from: perryjay on 12 Jul 2011, 09:05:35 am ---FYI, I picked up and ran an AP on my GPU last night. That could have been the problem. Everything is back up to speed after rebooting but my MB tasks on GPU are running high priority. That should settle down after a couple run here soon. I also have a few APs waiting so we shall see what happens.
--- End quote ---
Something to watch: I have no idea if Raistmer included any boincApi fixes for modern Cuda 4.0 drivers, or if they'd be needed under OpenCL running as they most definitely are under Cuda. One way to find out would be to repeatedly exit Boinc (shutting down the AP while in progress) [or just snooze/unsnooze etc) & see if it triggers a sticky downclock or not. If so, then you'll just have to slap Raistmer around a bit to fix it. [ I mean ask nicely... :D]
Jason
--- End quote ---
Raistmer hasn't spoken about doing any api changes on any of his apps for Cuda 4 drivers, his apps also consume large amounts of CPU time when running with Cuda 4 drivers (when running on their own),
if there are other apps running like CPU apps, they manage to claw back some of that CPU time, but i think the elapsed time of the OpenCL tasks suffers,
Claggy
Jason G:
--- Quote from: Claggy on 12 Jul 2011, 03:35:49 pm ---Raistmer hasn't spoken about doing any api changes on any of his apps for Cuda 4 drivers, his apps also consume large amounts of CPU time when running with Cuda 4 drivers (when running on their own),
if there are other apps running like CPU apps, they manage to claw back some of that CPU time, but i think the elapsed time of the OpenCL tasks suffers,
--- End quote ---
Hmm, Well most of the Cuda 4 driver issues with actual cuda code, so far, have turned out to be a consequence of the underlying OS/driver changes, and are remedied by changing boincApi to behave a bit more threadsafe [to get back some stability], and taking into consideration the underlying memory model changes [to get back some performance+ a bit extra in some cases].
I'd expect eventually they'd apply to OpenCL as well, but didn't expect that yet. Oh well, at least before it becomes a real problem for Raistmer on Ati/OpenCL, we should have most of the kinks ironed out & techniques improved on the Cuda side.
[Edit:] do newer Ati drivers 'appear' to be getting slower as well for old-school coding techniques ?
Mike:
--- Quote ---[Edit:] do newer Ati drivers 'appear' to be getting slower as well for old-school coding techniques ?
--- End quote ---
When the setup is working properly no.
But there are some cicumstances some GPUs dont work well on each setup.
Will ty that lout on my sons PC as soon i find some time.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version