Message boards : Questions and problems : ATi GPU Supporting?
Message board moderation
Author | Message |
---|---|
Send message Joined: 1 Sep 09 Posts: 1 ![]() |
Is there any ATi GPU Supporting? I am using 6.10.0 HD4850 win7 x64 I just add GPUGILD,Collatz Conjecture,AQUA@home,MilkyWay@home. None of them are using my GPU. I have check the box "Use GPU while computer in use" but the GPU usage is 0% all the time. What should i do? ![]() |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
6.10.0 is an alpha release. It's been available for all of 10 days. You can't expect miracles in that timeline. Most projects will wait until the core client is publicly released, not in alpha or beta test. Milkyway will be able to use the Ati GPU, but through the anonymous platform. See their forums for details on that. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
The OP may be thinking of the NVidia/CUDA release in December last year, when both the BOINC client and a science application were made available at the same time - first as Beta, then a week later as a public recommended release. That exercise proved that, although it's hard to fully test a client without an app, or vice-versa, nevertheless such testing is vital: it took a further month to get the science app working without crashing, and even longer to get the bugs out of the client. I would imagine that private alpha testing has already started at some projects: later, there may be a call for suitably-motivated volunteers to participate in more open Beta testing. It would be in everybody's best interests for that testing to be allowed to run its course, so that the applications when released don't suffer the problems that the premature CUDA release suffered. |
Send message Joined: 19 Jan 07 Posts: 1179 ![]() |
That exercise proved that, although it's hard to fully test a client without an app, or vice-versa, nevertheless such testing is vital: it took a further month to get the science app working without crashing, and even longer to get the bugs out of the client. What do you mean "even longer"? There are still bugs, the scheduler hasn't worked right ever since CUDA support was added. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
That exercise proved that, although it's hard to fully test a client without an app, or vice-versa, nevertheless such testing is vital: it took a further month to get the science app working without crashing, and even longer to get the bugs out of the client. What I said - even longer. Eight months and counting. And as fas as I'm concerned, there were bugs before, there are bugs now, and there always will be bugs. BOINC is that sort of project. The ratio of bugs to features varies from time to time, and maybe the GPU developments (plural) have added bugs even faster than they have added features - though I find the version I'm currently using (v6.6.37 with Thyme Lawn's [trac]#139[/trac] extensions) is fairly predictable if you don't push the boundaries too hard. [That reminds me - I must write up a work fetch bug report for multi-cores, long tasks, short cache, and a big multi-threaded app in the mix. It doesn't fetch enough tasks to keep all cores active with single-threaded apps, so it runs the MT as a spare single-threaded app. Messy.] |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.