I would test it but I'm running XP, and XP isn't allowed to the party. This seems to have been what was recently used to reclaim the "fastest card evar" crown. "What we notice is that the beta Catalyst 12.11 driver does, in fact, deliver a massive performance boost in a majority of the games we're testing. Nvidia only manages to maintain an advantage in long-time strongholds like Battlefield 3 and Batman: Arkham City, even though AMD jumps from 25 to 30 percent in Battlefield 3, practically making it a draw..."

The story & drivers are here, With CodeXL and APP SDK 2.8, our highest performing SDK to date which leaps past the competition in performance Will this translate into immediately better SETI times?

I'd love to know if there is a good reason for me to spend the 40 bucks for Windows 8...

It will probably take some time til seti benefits.
Simple driver change wont help much i guess.
Apps needs to be recompiled and tested carefully.

---

With each crime and every kindness we birth our future.

am running new sdk in win8,it is running much faster in primegrid and astropulse

no errors yet.

some one try this with opencl compatible nvidia should work please post.

will post as I see more.

---

It will probably take some time til seti benefits.
Simple driver change wont help much i guess.
Apps needs to be recompiled and tested carefully.

Maybe, but, those games weren't recompiled for the new driver. I ran the SDK updater in XP but it doesn't appear to have done a thing with the old driver. Another link here; Downloads

Games are different.
But SDK is for developers.

Actual apps might benefit.
Will test that as soon i`ve got some time.

---

With each crime and every kindness we birth our future.

cpu amd gpu temp dropping so far so good.

---

I have seen a 25% boost in performance while running Einstein/OpenCL via an AMD 7970. The increase was with Linux beta driver 12.11 over driver 12.10 and APP SDK 2.7. I have not tested with Seti yet.

So far, I very much like the performance of the 7970 with driver 12.11. Plus the PCI-E 3.0 support works out of the box in Linux and Windows with the socket 2011 processors which is a nice bonus. No hacks are required like with the NVIDIA drivers and there is complete stability.

---

The APP runtime included with SDK 2.8 is the exact same version (10.0.1084.2) included with Catalyst 12.11 betas 8 and 11.

As far as I can tell there is no need to install the SDK, just the latest 12.11 beta driver.

The GPU utilization bug still exists, so, continue idling those CPU cores.

The APP runtime included with SDK 2.8 is the exact same version (10.0.1084.2) included with Catalyst 12.11 betas 8 and 11.

As far as I can tell there is no need to install the SDK, just the latest 12.11 beta driver.

The GPU utilization bug still exists, so, continue idling those CPU cores.

Like i mentioned earlier APP SDK is for developers only.

The "GPU utilzation bug" is not really a bug its a feature.

---

With each crime and every kindness we birth our future.

The APP runtime included with SDK 2.8 is the exact same version (10.0.1084.2) included with Catalyst 12.11 betas 8 and 11.

As far as I can tell there is no need to install the SDK, just the latest 12.11 beta driver.

The GPU utilization bug still exists, so, continue idling those CPU cores.

Yes, it's in the first post "Catalyst 12.11", which at this point, is still in Beta. You can find it here AMD Catalyst™ 12.11 Beta Driver Or, if you don't like Betas, you can install the AMD Catalyst™ 12.10 Driver from here Graphics Drivers & Software , then install the 2.8 Runtime from here Windows Vista® SP2 / Windows® 7 . Note there are 3 parts to that SDK, you only need the RunTime Part. Obviously, the easiest thing to do is install the "Catalyst™ 12.11 Beta Driver"...

Since you have installed the Catalystâ„¢ 12.11 Beta Driver, as in this article, have you noticed an approximate 25% performance increase?

without running a test batch through with and without the new sdk I was premature

in saying it was faster.

but any improvement in opencl will be a help in seti though it may take re-

compiles of the clients to see this.

testing should be minimal the math library's still do the same math,they have

just been optimized to do it more efficiently.

the bottom line here is that opencl is as close to assembly language as anyone

program's any more.

it talks directly to the hardware. Any speed improvement here speeds up everything.

---

Since you have installed the Catalystâ„¢ 12.11 Beta Driver, as in this article, have you noticed an approximate 25% performance increase?

I haven't benchmarked. I have a relatively modest 6670 and I don't expect great things from it. With each new driver/runtime I just check to see if the gpu utilization bu^h^hfeature is fixed.

I've d/led the files. I'll install in the morning and see how they run

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

I've d/led the files. I'll install in the morning and see how they run

Thanks. I was getting all worked up about upgrading to Win 8 until I remembered they are working on a version of the GPU apps that work on a Mac. I do have Lion installed on this machine. I think I'll just wait for a Lion version of the SETI GPU apps instead of rushing into some new flanged Windows OS. I'll have to think about it...

2 all who upgrade their drivers looking for speedup:
don't forget to delete binary cached kernels from project directory then. App will recompile them with new driver and then will have a chance to recive some speedup from better compiler in new driver.
But beware, Cat 12.10 (for example) known to produce invalid binaries (results can not validate). Cat 12.11 beta 8 looks clean though.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

My AMD system was finally able to pickup a few AP tasks. The processing time via driver 12.11 appears to be faster than what I am seeing via my GTX 580s but it is hard to tell for sure as processing time varies significantly from one task to another. GPU load ranges from 59-77%.

---

2 all who upgrade their drivers looking for speedup:
don't forget to delete binary cached kernels from project directory then.

Sorry Raistmer, what are those files named? All I see are the kernel source .cl files.

One is called Multibeam_Kernels_r390.cl_turks.bin_V6.
The other r_390_yourhostname.wisdom.

---

With each crime and every kindness we birth our future.

Make sure you keep copies of any removed kernel files in case you need to revert back to them,

Claggy

Please explain "delete binary cached kernels from project directory".
I cannot find any OpenCL file apart from those in a slot directory.