I would of thought the standard app would of been properly optimised for my old Core 2 Quad (SSE 4.1) by now, & so the optimised app would make no difference, am I wrong?

Whilst I'm at it, the other question is whether my HD 5850 would benefit from an optimised app?

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Code optimization often takes the form of finding more efficient ways to accomplish the needed result, not just adapting the code better to fit particular hardware.

I think you'll find at any given moment that the current Lunatics release will run SETI work faster than the stock SETI release on just about any hardware it supports.

Try it if you like.

---

Yes, current builds are definitely faster.
You can use the 64 bit installer so you will get the 64 bit apps for your CPU and the OpenCL app for your 5850 is also faster.

You can download the installer either from Lunatics website or from my website.

---

With each crime and every kindness we birth our future.

I would of thought the standard app would of been properly optimised for my old Core 2 Quad (SSE 4.1) by now, & so the optimised app would make no difference, am I wrong?

Whilst I'm at it, the other question is whether my HD 5850 would benefit from an optimised app?

For the stock app they try to make it generic as possible so that that the same exe will run on most systems. So kind of greater compatibility & less optimized.
The highest level extension may not always be the fastest on your machine. So if you want to install the optimized apps you can try each one to find the best run times for your system.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Cool, ok thanks I'll try it :).

I'll switch when I have a dozen or so results from my GPU so I can see & post before & after times for both CPU & GPU.

Std app C2Q 3.6 GHz :-

3681398891 1567447745 15 Aug 2014, 8:48:11 UTC 17 Aug 2014, 22:48:09 UTC Completed and validated 11,111.01 ... 11,056.17 92.83 SETI@home v7 v7.00
3681399944 1567448155 15 Aug 2014, 8:48:11 UTC 17 Aug 2014, 21:20:32 UTC Completed and validated 3,477.21 ... 3,457.50 35.03 SETI@home v7 v7.00
3681399945 1567448161 15 Aug 2014, 8:48:11 UTC 17 Aug 2014, 21:20:32 UTC Completed and validated 3,543.94 ... 3,509.84 31.90 SETI@home v7 v7.00
3681399947 1567448151 15 Aug 2014, 8:48:11 UTC 17 Aug 2014, 21:20:32 UTC Completed and validated 3,512.86 ... 3,493.44 33.48 SETI@home v7 v7.00
3681399949 1567448167 15 Aug 2014, 8:48:11 UTC 17 Aug 2014, 22:48:09 UTC Completed and validated 3,395.42 ... 3,384.05 33.50 SETI@home v7 v7.00
3681336369 1567417525 15 Aug 2014, 7:47:31 UTC 17 Aug 2014, 19:53:55 UTC Completed and validated 3,452.54 ... 3,430.48 35.35 SETI@home v7 v7.00
3681336370 1567417531 15 Aug 2014, 7:47:31 UTC 17 Aug 2014, 19:53:55 UTC Completed and validated 3,561.53 ... 3,528.21 31.91 SETI@home v7 v7.00
3681219427 1567361825 15 Aug 2014, 5:53:07 UTC 17 Aug 2014, 21:20:32 UTC Completed and validated 10,696.33 ... 10,639.14 96.37 SETI@home v7 v7.00
3681219688 1567361914 15 Aug 2014, 5:53:07 UTC 17 Aug 2014, 19:53:55 UTC Completed and validated 5,798.64 ... 5,757.36 53.08 SETI@home v7 v7.00
3680974531 1567244465 15 Aug 2014, 1:46:50 UTC 17 Aug 2014, 18:27:28 UTC Completed and validated 9,626.96 ... 9,535.00 87.97 SETI@home v7 v7.00
3680974819 1567244674 15 Aug 2014, 1:46:50 UTC 17 Aug 2014, 15:47:01 UTC Completed and validated 9,491.60 ... 9,367.52 90.17 SETI@home v7 v7.00
3680879918 1567199488 15 Aug 2014, 0:16:00 UTC 17 Aug 2014, 16:52:24 UTC Completed and validated 12,371.62 ... 12,270.66 99.53 SETI@home v7 v7.00
3680879919 1567199494 15 Aug 2014, 0:16:00 UTC 17 Aug 2014, 15:47:01 UTC Completed and validated 12,388.81 ... 12,263.00 113.09 SETI@home v7 v7.00
3680818723 1567170397 14 Aug 2014, 23:14:35 UTC 17 Aug 2014, 15:47:01 UTC Completed and validated 12,585.54 ... 12,482.50 104.94 SETI@home v7 v7.00
3680694653 1567111167 14 Aug 2014, 21:20:06 UTC 17 Aug 2014, 13:25:40 UTC Completed and validated 12,237.96 ... 12,156.33 110.23 SETI@home v7 v7.00

Oh btw, should I be dedicating a CPU core for the GPU to crunch at best speed?

[update]
Answer would seem to be yes as GPU load is hovering mostly at 0%! Even though it is crunching & GPU temps are up, but low for crunching (66C atm & current at 9-15A).
[update 2]
Dedicated a core & now GPU load is upto 92-93% & VDDC current at 27-29A (GPU o/c to 850 MHz btw). So far GPU temp is upto 77C

Damn, grx driver had locked up & recovered, now twice!....... time to down clock...

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Hmm, it's not down to GPU clock speed, after a reboot the driver locked up again, & this time it was at default speed.

I thought the lock ups only happened after I dedicated a CPU to the GPU, but after 'un-dedicating' it it still locked up, so I've had to suspend GPU crunching on my 5850 for now :(.

Any ideas anyone? (using Cat 13.1 btw, was forced to for MW@H)

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Hmm, it's not down to GPU clock speed, after a reboot the driver locked up again, & this time it was at default speed.

Any ideas anyone? (using Cat 13.1 btw, was forced to for MW@H)

Cat 13.1 has some issues generating binaries.
I`d suggest Cat 13.12.

---

With each crime and every kindness we birth our future.

Damn, ok thx, I thought you might say that, oh well I suppose I can just go back to 13.1 as & when I go back to MW@H.

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Installed 13.12, rebooted, still get driver lock ups about every 30-60s :(.

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Installed 13.12, rebooted, still get driver lock ups about every 30-60s :(.

Did you do a full removal of the old Cat 13.1 or just install the new one over the top?
You can use
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
to get all of the old driver bits out of the system.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Over the top, I thought it would be ok for going upwards in drivers, I'll try a full clean out.

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Tried to use manager to un-install 13.12, on rebooting it BSOD (I recall that happening before!), used system restore which took it back 13.1, then used un-install manager & DDU to remove 13.1, rebooted, installed 13.12 & tried GPU crunching, driver locked up again after ~30s :(

Any further ideas?

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Delete the Binaries from 13.1. You have to do it manually.
Delete everything in the setiathome.berkeley.edu folder ending in .bin, .bin_V6, .bin_V7, and .wisdom

What are binaries & where are they? (I've just deleted the C:/AMD 13.1 folder).

..... and now deleted those SETI files, although the v6 file wasn't there.

Btw why would I need to delete the SETI files?

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

They are Not SETI files. The Binaries are generated by the App depending on the Driver. They are Driver Specific. The Old Apps didn't take driver versions into consideration, hence the Cluster. The New Apps will have the Driver version included in the File name, such as; AP_clFFTplan_ATIRadeonBartsPROPrototype_32768_r2559.bin_13.3.0_12Jun10201422
Hopefully, no more clusters.

Oh I thought the binaries & .bin files were 2 different things, I see what you mean now ;). I did say I didn't know what the binaries were.

What do you mean by clusters? clusters of what?
What are you referring to when you say old & new apps? (I haven't installed the optimised apps yet).

Thx for your help so far btw :)

Oh & it seems to of fixed it, no more driver lock ups :)

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

What do you mean by clusters? clusters of what?

I would call having to explain to people how to delete files they usually don't know how to find every time they changed the driver a Cluster ....

Glad to hear it's working now.

New AstroPulse Apps are being tested, Astropulse 7,00 released for Linux 32&64, Win 32&64, Win32+AMD/NVIDIA/Intel GPU

Ah ok, well the 'cypress_xx_r1831' files have all returned, as has the v7 file, I can see no differences in the file name (old ones in recyc bin atm), yet the deletion worked!
Could the files be different versions with identical names??

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP@H.

Main rig - Ryzen 5 3600, 32GB DDR4 3200, RX 580 8GB, 500GB Samsung 970 Evo+, Win 10
2nd rig - i7 4930k @4.1 GHz, 16GB DDR2 1866, HD 7870 XT 3GB (DS), Win7 64bit

Ah ok, well the 'cypress_xx_r1831' files have all returned, as has the v7 file, I can see no differences in the file name (old ones in recyc bin atm), yet the deletion worked!
Could the files be different versions with identical names??

Yes of course.

I suggest to use the installer since more recent apps are more mature.

---

With each crime and every kindness we birth our future.

Yes, that's one problem with the current OpenCL Apps. The Binaries have the same name no matter which driver is being used. Then the App tries to use the Binary that was complied with a different driver. It usually doesn't work very well. The Binaries have to be deleted manually, or by a project detachment. Adding the Driver Version to the File Name should solve that problem.