want to run on a AGP GPU


log in

Advanced search

Message boards : Number crunching : want to run on a AGP GPU

Previous · 1 · 2
Author Message
Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1324590 - Posted: 4 Jan 2013, 14:46:42 UTC - in response to Message 1324581.

What you want to know is the max work group size of the card.

Run CLinfo in a cmdline window and check this please.

Thanks for help. CLInfo gives four different results relating to group size:

Max work group size: 128
Kernel Preferred work group size multiple: 32
Max work group size: 1024
Kernel Preferred work group size multiple: 1

Cheers

Hal: Looking at those files now...
____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1324596 - Posted: 4 Jan 2013, 14:57:06 UTC - in response to Message 1324585.

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?

Cheers

____________

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 22383
Credit: 29,309,376
RAC: 23,715
Germany
Message 1324597 - Posted: 4 Jan 2013, 15:03:23 UTC

You can run astropulse with stock app.
r_555 is out dated.

You just need to check astropulse V6 in your preferences page.

____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1324598 - Posted: 4 Jan 2013, 15:08:30 UTC - in response to Message 1324597.

You can run astropulse with stock app.
r_555 is out dated.

You just need to check astropulse V6 in your preferences page.

Ok thanks. I've had that app selected all along, so I guess there just are no WU's available currently.

In case nothing comes along before the outage, I could test with my backup project MilkyWay. I recall that they have WU's for ATI.

Cheers

____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1324654 - Posted: 4 Jan 2013, 18:21:04 UTC

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.

MilkyWay project sent boinc a notice saying "GPU lacks necessary double precision extension".

If it doesn't end up working, I still have other uses for this card on the system, but would be nice to crunch SETI with it too.

Cheers
____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1324828 - Posted: 5 Jan 2013, 7:47:40 UTC
Last modified: 5 Jan 2013, 8:10:45 UTC

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 :)

Cheers
____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1325158 - Posted: 6 Jan 2013, 4:05:03 UTC
Last modified: 6 Jan 2013, 4:07:52 UTC

Everything still working good with GPU crunching.

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.

Cheers
____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 3963
Credit: 31,844,974
RAC: 10,703
United Kingdom
Message 1325226 - Posted: 6 Jan 2013, 12:14:33 UTC - in response to Message 1325158.

The only reason i see why a GPU wouldn't be OpenCL capable is, if the CPU doesn't have a minimum of SSE2, like on my XP3200+/AGP HD4650/PCI 8400GS:

Computer 5306154

Claggy

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 22383
Credit: 29,309,376
RAC: 23,715
Germany
Message 1325296 - Posted: 6 Jan 2013, 14:36:11 UTC
Last modified: 6 Jan 2013, 14:42:37 UTC

You can`t be certain.

Minmum system requirement for OpenCL is RV 770.
The HD 4650 is RV 730.

If you check the AMD Dveloper site HD 4 cards are completely removed from compatibility list.

http://developer.amd.com/tools/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/system-requirements-driver-compatibility/
____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 3963
Credit: 31,844,974
RAC: 10,703
United Kingdom
Message 1325320 - Posted: 6 Jan 2013, 15:31:16 UTC - in response to Message 1325296.

You can`t be certain.

Minmum system requirement for OpenCL is RV 770.
The HD 4650 is RV 730.

If you check the AMD Dveloper site HD 4 cards are completely removed from compatibility list.

http://developer.amd.com/tools/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/system-requirements-driver-compatibility/

That's for APP SDK 2.8, we're using APP SDK 2.6 which had a totally different list and is no longer available, all the HD4*** GPUs had Beta support at the time,

Searching the Net, i've found the requirements for APP SDK 2.7, showing that the Beta level GPUs being deprecated on APP SDK 2.7:

http://amddevcentral.com/tools/hc/AMDAPPSDK/pages/DriverCompatibility.aspx

and http://www.gpu-tech.org/content.php/179-AMD-APP-SDK-2.6-is-available-for-download

has an attachment showing APP SDK 2.6 requirements: http://www.gpu-tech.org/attachment.php?s=916d424312f087bb948e97df30b985e0&attachmentid=427&d=1323728699

Where HD4670, HD4650, HD4550 and HD4350 GPUs are shown as being supported.

Claggy

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1325334 - Posted: 6 Jan 2013, 16:48:32 UTC

Thanks for replies and the information.

Got me thinking about how long my AGP level cards will remain useable for SETI. Do you think that SETI project will be having reasons for moving from v2.6 of the SDK anytime pretty soon?

Cheers

____________

Profile Mike
Volunteer tester
Avatar
Send message
Joined: 17 Feb 01
Posts: 22383
Credit: 29,309,376
RAC: 23,715
Germany
Message 1325340 - Posted: 6 Jan 2013, 17:02:37 UTC - in response to Message 1325334.

Thanks for replies and the information.

Got me thinking about how long my AGP level cards will remain useable for SETI. Do you think that SETI project will be having reasons for moving from v2.6 of the SDK anytime pretty soon?

Cheers


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


____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1325349 - Posted: 6 Jan 2013, 18:16:12 UTC - in response to Message 1325340.


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

____________

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1325397 - Posted: 6 Jan 2013, 22:30:28 UTC

So honorable mentions to HAL9000, Ianab, Claggy and Mike (all volunteer testers) for the resources, information and interest in my GPU project.

Purpose of the "GPU project": I have had 3 P4's churning SETI for the past while and I have decided to shelve one of them and update two of them with GPU capability. Looks like that will work out now.

I'll also pretty soon add a quad core G0 stepping Q6600 as a dedicated cruncher. I'll see about clocking up the speed on that and also look at adding a fairly robust PCI-E GPU to it later on.

So that will be the crunching farm for the time being :)

Thanks again

____________

Profile Raistmer
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 16 Jun 01
Posts: 3276
Credit: 40,793,690
RAC: 60,070
Russia
Message 1325410 - Posted: 6 Jan 2013, 23:59:32 UTC - in response to Message 1325349.


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).
____________
News about SETI opt app releases: https://twitter.com/Raistmer

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1325413 - Posted: 7 Jan 2013, 0:31:51 UTC - in response to Message 1325410.
Last modified: 7 Jan 2013, 0:34:54 UTC


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 :)
____________

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 3963
Credit: 31,844,974
RAC: 10,703
United Kingdom
Message 1325414 - Posted: 7 Jan 2013, 0:37:19 UTC - in response to Message 1325413.
Last modified: 7 Jan 2013, 0:40:18 UTC


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

Aero
Send message
Joined: 4 Feb 04
Posts: 29
Credit: 1,029,657
RAC: 4,166
Message 1325488 - Posted: 7 Jan 2013, 11:46:44 UTC - in response to Message 1325414.
Last modified: 7 Jan 2013, 11:50:50 UTC


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.

Cheers
____________

Previous · 1 · 2

Message boards : Number crunching : want to run on a AGP GPU

Copyright © 2014 University of California