Forum > GPU crunching
CUDA_V12_app
Raistmer:
Explanation not very complex:
app needs CPU to feed GPU with data. CPU busy by boinc.exe, this process has higher priority than app so app starve. GPU stays idle. So, low total RAC.
I don't know value that will fit to your config. Try to reduce cache until boinc.exe will almost not eat CPU.
Lord Asmodeus:
ATM I don't ask any WU, I still got 1250 to go. I'm not really conviced by your idea, my GPU seems to work all the time, I can tell by the temp of the water (watercooled PC). Moreover I have a quad core so I don't see why a boinc.exe taking 100% of one core would affect the GPU.
When I got this card some 3 months ago, it was doing the WUs in around 10 minutes, and now it's twice that, I wonder why.
msattler:
--- Quote from: Lord Asmodeus on 07 Aug 2009, 07:32:31 pm ---ATM I don't ask any WU, I still got 1250 to go. I'm not really conviced by your idea, my GPU seems to work all the time, I can tell by the temp of the water (watercooled PC). Moreover I have a quad core so I don't see why a boinc.exe taking 100% of one core would affect the GPU.
When I got this card some 3 months ago, it was doing the WUs in around 10 minutes, and now it's twice that, I wonder why.
--- End quote ---
There was a change made at Seti which roughly doubled the length of MB WU's............to increase the science a bit, but also to try to tame the bandwidth as well.
But don't fret.......if you check your completed results, you should see that the awarded credits have roughly doubled too.
Probably not a problem with your setup or card.
Raistmer:
--- Quote from: Lord Asmodeus on 07 Aug 2009, 07:32:31 pm ---ATM I don't ask any WU, I still got 1250 to go. I'm not really conviced by your idea, my GPU seems to work all the time, I can tell by the temp of the water (watercooled PC). Moreover I have a quad core so I don't see why a boinc.exe taking 100% of one core would affect the GPU.
When I got this card some 3 months ago, it was doing the WUs in around 10 minutes, and now it's twice that, I wonder why.
--- End quote ---
Well, look at msattler post, did you accounted that task changed indeed?
About BOINC-related things, you can simply check if it applies to your config or not - just leave host running few hours w/o reboots and BOINC restarts than launch task manager and see how many CPU time was consumed by boinc.exe + boincmgr.exe processes. If only few seconds - well, your BOINC behaves good. If minutes - you should decrease cache probably.
Lord Asmodeus:
Well the WUs my CPU crunched were not taking double the time so I didn't think it was a change like that. But now they are.
A few days ago I asked again some WUs (my GPU had nothing left), after having set the cache to one day, and I received hundreds and hundreds of them ! Now I restarted the "not asking WUs" part, and used the rebranding utility to compensate the lack of GPU WUs. The old script wasn't working anymore, but the exe is fine. With less than 1000 WU boinc.exe takes almost no CPU time, so around 4-5 days of cache should be the sweet spot. But I want to start from fresh so I'll finish up what I have and then reinstall.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version