Forum > GPU crunching
V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use
Josef W. Segur:
--- Quote from: FalconFly on 08 May 2009, 08:46:06 am ---...
Message from server: No work sent
Message from server : No work is available for Astropulse
At this time, however, there are 24592 AP WorkUnits and 120065 MB WorkUnits ready to send.
...
--- End quote ---
Astropulse is the old application, it is quite likely there is no work available for that. Astropulse v5 is the new one, those 24592 tasks should be all or almost all for that application. Those server messages are exact, they'll say "Astropulse v5" if that is what isn't available.
However, the "no work is available" message refers to the 100 slots in the shared memory between the Feeder and Scheduler. At any moment, there may well be no work of a particular kind there, and the Scheduler can't send what it doesn't know about.
If the server message only reports about "Astropulse", that may mean your project preferences have somehow been set to only accept that kind of work.
Joe
Raistmer:
CUDA 2.2 benchmarking results:
1) New CUFFT can't run with 182.50 driver
2) new (2.2) CUDA runtime+ current CUDA MB can operate with 182.50 driver
3) there is small speedup from using CUDA_RT of 2.2 and there is no speedup from rebuilding current CUDA MB sources with CUDA 2.2
4) there is significant speedup (it even offsets lack of OCing on my GPU) from using current drivers (185.85) + CUDA RT 2.2 + CUFFT 2.2 (again, all builds show that speedup, not only freshly rebuilt one).
Summary: for those who can go with new drivers it's worth to upgrade to CUDA 2.2 runtime w/o upgrading current CUDA MB app.
For all others it's worth to try to use new cudart.dll + old cufft.dll.
(new CUDA 2.2 runtime attached (cudart.dll + cufft.dll )
Don't forget to update video driver to 185.85 version.
[attachment deleted by admin]
KarVi:
Thanks for the heads up Raistmer.
I´m trying the newest drivers (185.85), with CUDA 2.2 supplied by you, on my 9500.
Looking forward to see the results.
FalconFly:
--- Quote from: Josef W. Segur on 08 May 2009, 12:54:02 pm ---
Astropulse is the old application, it is quite likely there is no work available for that. Astropulse v5 is the new one, those 24592 tasks should be all or almost all for that application. Those server messages are exact, they'll say "Astropulse v5" if that is what isn't available.
However, the "no work is available" message refers to the 100 slots in the shared memory between the Feeder and Scheduler. At any moment, there may well be no work of a particular kind there, and the Scheduler can't send what it doesn't know about.
If the server message only reports about "Astropulse", that may mean your project preferences have somehow been set to only accept that kind of work.
Joe
--- End quote ---
Alright, so I will give it another shot and add more patience ;)
I've read that BOINC 6.6.20 does not work with the V10, so which BOINC version is suitable ?
(Note - I'm using the Windows 7 RC 64bit, not sure if that affects the whole thing)
Richard Haselgrove:
--- Quote from: Raistmer on 08 May 2009, 06:46:49 pm ---CUDA 2.2 benchmarking results:
1) New CUFFT can't run with 182.50 driver
2) new (2.2) CUDA runtime+ current CUDA MB can operate with 182.50 driver
3) there is small speedup from using CUDA_RT of 2.2 and there is no speedup from rebuilding current CUDA MB sources with CUDA 2.2
4) there is significant speedup (it even offsets lack of OCing on my GPU) from using current drivers (185.85) + CUDA RT 2.2 + CUFFT 2.2 (again, all builds show that speedup, not only freshly rebuilt one).
Summary: for those who can go with new drivers it's worth to upgrade to CUDA 2.2 runtime w/o upgrading current CUDA MB app.
For all others it's worth to try to use new cudart.dll + old cufft.dll.
(new CUDA 2.2 runtime attached (cudart.dll + cufft.dll )
Don't forget to update video driver to 185.85 version.
--- End quote ---
I've applied the full 'triple treatment' (driver, runtime and fft) to my rigs (2 x 9800GT and a 9800GTX+), which run the stock v6.08 from Berkeley. Good impression all round: display seems smoother, app runs faster, and I'm even seeing signs of lower CPU loading (though maybe that's just BOINC's way of telling me the boxes were due a reboot ;D ). I'm still not going to risk throwing a VLAR into the mix, but apart from that we seem to have a winner.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version