BOINC doesn't benchmark the GPU at this time. It uses the manufacture specified number for the card. Which is probably 383, or 416 GFLOPS for the card.
Right now there are only GPU Apps to download. The app "AP 6.01 r555 ATI OpenCL" is the most recently. However, "ATI OpenCL MultiBeam 6.10 App (rev177) for Windows" is an older version. I am not sure if the most recent version (r390) is subject to the licensing issue or not. It is possible to create an app_info.xml file that would let you run the stock CPU apps and the optimized GPU apps, but it can be a bit tricky.

Hi,
I just downloaded the AP v6.01 r555 for ATI GPU with OpenCL capabilities. Can this be used without creating the "app_info.xml"?

In any case, I take it that the SETI project servers are definitely not going send any apps for the GPU automatically? Must use one of those builds?

Increased my buffers to two days to spur some more WU's. WU's came but no astropulse yet.

Then again, I allow astropulse on CPU and sometimes they are sent almost exclusively and other times I get only SetiEnhanced WU's. In past week I've noticed only one astropulse in midst of many SetiEnhanced.

Just noticed that the HD4650 has picked up some Astropulse v6 opencl WU's. The card is running 7C above idle temp. In the "Status" column for the running Astropulse WU it says "Running (0.386 CPU + 1 ATI)". In addition to that Astropulse WU, the HT P4 3.2 CPU is also running two SETI Enhanced WU's. So the computer has three WU's going simultaneously.

Looking good. Thanks again everyone for all the input and information :)

Does this show that any AGP HD4650 card will be compatible with stock Astropulse?

In this thread there was some uncertainty whether my card would be compatible with stock Astropulse. I'm wondering whether that uncertainty was regarding my particular GigaByte card or regarding AGP HD4650 GPU's generally.

The reason I ask is that I might keep an eye out for a second used AGP HD4650 (or HD4670). If I end up finding a different brand AGP HD4650, I'm wondering whether I can be certain that it will also be compatible before I buy it.

It doesn´t depend on seti.
Raistmer is writing the ATI apps.
He mentioned not to move to SDK 2.8 for now.

Oh ok thanks. I guess I'll be following along on that forum now as well.

In regards to that, I think S@H is unique in that they are "in it for the long haul" more-than or in a different sense than other projects. Probably more than other projects they need to keep a long view about keeping people interested. (That probably doesn't apply to most anyone writing in here obviously. Though I've been away from it at times, I consider myself to be a true believer in SETI).

But considering that, I think it makes sense for them to keep supporting an older SDK (even after moving to a new one) as long as there are a fair number of crunchers out there that require the older SDK (assuming of course that they are still getting useable results in comparison to whatever newer build there is).

It doesn´t depend on seti.
Raistmer is writing the ATI apps.
He mentioned not to move to SDK 2.8 for now.

Oh ok thanks. I guess I'll be following along on that forum now as well.

In regards to that, I think S@H is unique in that they are "in it for the long haul" more-than or in a different sense than other projects. Probably more than other projects they need to keep a long view about keeping people interested. (That probably doesn't apply to most anyone writing in here obviously. Though I've been away from it at times, I consider myself to be a true believer in SETI).

But considering that, I think it makes sense for them to keep supporting an older SDK (even after moving to a new one) as long as there are a fair number of crunchers out there that require the older SDK (assuming of course that they are still getting useable results in comparison to whatever newer build there is).

Cheers

To build Brook+ based AP now I need development machine separate from my main dev one. Only that equipped with Brook+ supporting SDK. So don't expect frequent updates for Brook+ app, time investment into developing for latest GPUs will bring better results now. But Brook+-capable GPUs still usable with SETI. It's HD2000 and up. In other words we support much more old GPUs than AMD itself (they announced recently that HD4xxx (RV7xx) not supported already).
____________

To build Brook+ based AP now I need development machine separate from my main dev one. Only that equipped with Brook+ supporting SDK. So don't expect frequent updates for Brook+ app, time investment into developing for latest GPUs will bring better results now. But Brook+-capable GPUs still usable with SETI. It's HD2000 and up. In other words we support much more old GPUs than AMD itself (they announced recently that HD4xxx (RV7xx) not supported already).

I take it that Brook+ is name for the AP used by 4000 series GPU. Thanks for the info on the current status of it. I agree that you should be primarily focused on the most current and most productive GPU's. That helps S@H function as best as possible.

Thanks though for sparing what time you can for those of us still chugging with AGP's :) Like I mentioned I'll be installing pretty soon a newer PCI-E GPU as well, so I'll be soon using your latest code as well.

Thanks for your ongoing work on GPU crunching with SETI. It's a great cause.

To build Brook+ based AP now I need development machine separate from my main dev one. Only that equipped with Brook+ supporting SDK. So don't expect frequent updates for Brook+ app, time investment into developing for latest GPUs will bring better results now. But Brook+-capable GPUs still usable with SETI. It's HD2000 and up. In other words we support much more old GPUs than AMD itself (they announced recently that HD4xxx (RV7xx) not supported already).

I take it that Brook+ is name for the AP used by 4000 series GPU. Thanks for the info on the current status of it. I agree that you should be primarily focused on the most current and most productive GPU's. That helps S@H function as best as possible.

Thanks though for sparing what time you can for those of us still chugging with AGP's :) Like I mentioned I'll be installing pretty soon a newer PCI-E GPU as well, so I'll be soon using your latest code as well.

Thanks for your ongoing work on GPU crunching with SETI. It's a great cause.

Cheers :)

No, you're running the OpenCL app, the Brook+ app is a Hybrid CPU/GPU app, mostly using the CPU with a little bit of GPU acceleration, it is mostly for HD3*** and earlier ATI GPUs that don't support OpenCL.

To build Brook+ based AP now I need development machine separate from my main dev one. Only that equipped with Brook+ supporting SDK. So don't expect frequent updates for Brook+ app, time investment into developing for latest GPUs will bring better results now. But Brook+-capable GPUs still usable with SETI. It's HD2000 and up. In other words we support much more old GPUs than AMD itself (they announced recently that HD4xxx (RV7xx) not supported already).

I take it that Brook+ is name for the AP used by 4000 series GPU. Thanks for the info on the current status of it. I agree that you should be primarily focused on the most current and most productive GPU's. That helps S@H function as best as possible.

Thanks though for sparing what time you can for those of us still chugging with AGP's :) Like I mentioned I'll be installing pretty soon a newer PCI-E GPU as well, so I'll be soon using your latest code as well.

Thanks for your ongoing work on GPU crunching with SETI. It's a great cause.

Cheers :)

No, you're running the OpenCL app, the Brook+ app is a Hybrid CPU/GPU app, mostly using the CPU with a little bit of GPU acceleration, it is mostly for HD3*** and earlier ATI GPUs that don't support OpenCL.

Claggy

Oh I see. And that Brook+ app is one of the apps available for being manually installed for those still running that hardware. So if at some point the SDK is changed from v2.6, then the same might happen with the OpenCL app that's built on the v2.6 SDK? So someone with a HD4xxx could then manually install the legacy app that was compiled prior to changing from v2.6 SDK?

But I guess that depends on what Raistmer can reasonably use his time and resources for and if it makes any sense at that point in time to keep HD4xxx's running with OpenCL. Also I guess depends on what happens with the installer issue.

In any case whatever happens, I'm happy that for now I got to enable GPU crunching on a computer that I would have otherwise shelved at this point :) It looks like that comp's throughput will go up by 5 to 6 times with the HD4650 GPU.