I´m running two BOINC clients at my machine since yesterday with catalyst 15.7 (Open CL 1800.8). So far some wu have been already valided, which is better than 100% invalids when running 2 wus in one client.
So there maybe a silver lining but it is still a little to early.
I looked to your PC with the two BOINC Clients...
It looks like '50/50' - 50% OK and 50% invalids - until now.
It don't look so well.
It's really disappointing and annoying that AMD 'added' this BUG to the new drivers.
We have very powerful VGA cards, but couldn't enjoy the whole performance of it.
It is kind of strange. When running two wus in one client, they fail 100%. Running two clients with one wu each results in valids and invalids for both clients. But sometimes even valids from each calculated at the same time...
However, most of the failing wu of my second client (http://einsteinathome.org/host/12094224/tasks) are inconclusive as well as the results of my wingman.
What we need is to prick the interest of the project dev's into looking at this from the projects app code point of view to narrow down the list of potential culprits causing tasks to fail when run concurrently.
Sadly, I doubt there are enough Hawaii and to a certain degree Tonga users here at Einstein (wanting to run multiple tasks) to make it worth the developers effort.
We are aware of the problem (thanks to those who reported it here). Currently we can't think of any possible way we could influence this from the app side, it is the driver's and OpenCL's responsibility to isolate the different processes from each other and if there is a failure to do so, what can we do (other than force people to run just one E@H GPU task at a time?)
I'm also not entirely convinced this is restricted to Hawaii and Tonga cards, I'm pretty sure I also see this on a 7790 'Bonaire'.
So we know running 2 x BRP or 2 x SETI GPU concurrently with the affected drivers can cause problems. What about 1 x BRP GPU + 1 x SETI GPU? Any experience with that ?
So just a quick thought: If Radeon 7790 (also R9 285?) has a similar problem then this looks like a problem with the GCN architecture? All the affected cards seem to have GCN >= 1.1, which means an increased number of asynchronous compute engines. They should increase the parallel processing power.
On a second note: I haven´t been able to track the changes in the opencl driver from 1445.5 (catalyst 14.4, 2 wus work but very slow) to 1526.3 (catalyst 14.8, faster but two wus will fail). Maybe someone knows what kind of performace improvements were done between these two versions.
I consider Einstein on Radeon 7790 in 2 streams. The AMD Catalyst 14.2 Beta Download V1.3 driver (opencl driver 1411.4) I have no errors of calculations. Newer I don't use the driver
because on them I can't lower videocard frequency, only dispersal is available that doesn't suit me. I think that all problems on new videocards are connected with OpenCL 2.0
So we know running 2 x BRP or 2 x SETI GPU concurrently with the affected drivers can cause problems. What about 1 x BRP GPU + 1 x SETI GPU? Any experience with that ?
Cheers
HB
Back in July when SETI ran out of work, my cards fell over to running both Einstein and MilkyWay at the same time on the cards. Never had any issues when running SETI and Einstein or SETI and MW at the same time on the same card. Evidently both Einstein and MW fight for contention of the OpenCL resources when run concurrently on the same card since I then produced errors on both projects. I had invalids on both projects and things returned to normal when SETI came back online and my normal mix of work resumed. I posted the errors over at MW in Message 63838.
I'm also not entirely convinced this is restricted to Hawaii and Tonga cards, I'm pretty sure I also see this on a 7790 'Bonaire'.
I setup a 'Bonaire' card recently. It's more recent than the 7790 - an R7 260X 2GB. My understanding (and it could be wrong) is that it's the same chip with more memory and at somewhat higher clocks. It also has a factory overclock. A local computer store had them on special so I decided to test one out.
I ran it at 2x, 3x and 4x but had some validate errors at 4x with no gain in performance. After deciding on 3x, and after the weather warmed significantly, it started producing some invalid results (~10%) so I downclocked both core and mem from 1175/1625 MHz to 1150/1600 MHz. That has seemed to get rid of the invalids for the moment. With even warmer weather on the way, I might reduce these a bit more.
So, I'm not seeing this 'concurrent tasks' problem with my particular 'Bonaire'.
Since getting my R9 390 I've had it pointed out to me that I've got quite a number of invalids. (Card installed 09/10/15) That was running 2 WU's at a time (Setting 0.5 in preferences)
I'm trying 1 at a time now but that's going to be painfully slow.
I´m running two BOINC
)
I´m running two BOINC clients at my machine since yesterday with catalyst 15.7 (Open CL 1800.8). So far some wu have been already valided, which is better than 100% invalids when running 2 wus in one client.
So there maybe a silver lining but it is still a little to early.
For anyone trying this method, I had to change the instructions from http://vyper.kafit.se/wp/index.php/2011/02/04/running-different-nvidia-architectures-most-optimal-at-setihome/ a little. First I had to use "--" for the arguments in the commandline instead of "-" and when connecting to the computer in the second client I had to use 127.0.0.1:9999 instead of localhost:9999. Credit to the user salvorhardin at the anandtech forum (http://forums.anandtech.com/showthread.php?t=2254389) for this.
I looked to your PC with the
)
I looked to your PC with the two BOINC Clients...
It looks like '50/50' - 50% OK and 50% invalids - until now.
It don't look so well.
It's really disappointing and annoying that AMD 'added' this BUG to the new drivers.
We have very powerful VGA cards, but couldn't enjoy the whole performance of it.
It is kind of strange. When
)
It is kind of strange. When running two wus in one client, they fail 100%. Running two clients with one wu each results in valids and invalids for both clients. But sometimes even valids from each calculated at the same time...
However, most of the failing wu of my second client (http://einsteinathome.org/host/12094224/tasks) are inconclusive as well as the results of my wingman.
RE: I have 4 AMD Radeon R9
)
Jezuss... doesn't come much more powerful than that!
RE: What we need is to
)
We are aware of the problem (thanks to those who reported it here). Currently we can't think of any possible way we could influence this from the app side, it is the driver's and OpenCL's responsibility to isolate the different processes from each other and if there is a failure to do so, what can we do (other than force people to run just one E@H GPU task at a time?)
I'm also not entirely convinced this is restricted to Hawaii and Tonga cards, I'm pretty sure I also see this on a 7790 'Bonaire'.
So we know running 2 x BRP or 2 x SETI GPU concurrently with the affected drivers can cause problems. What about 1 x BRP GPU + 1 x SETI GPU? Any experience with that ?
Cheers
HB
So just a quick thought: If
)
So just a quick thought: If Radeon 7790 (also R9 285?) has a similar problem then this looks like a problem with the GCN architecture? All the affected cards seem to have GCN >= 1.1, which means an increased number of asynchronous compute engines. They should increase the parallel processing power.
On a second note: I haven´t been able to track the changes in the opencl driver from 1445.5 (catalyst 14.4, 2 wus work but very slow) to 1526.3 (catalyst 14.8, faster but two wus will fail). Maybe someone knows what kind of performace improvements were done between these two versions.
I consider Einstein on Radeon
)
I consider Einstein on Radeon 7790 in 2 streams. The AMD Catalyst 14.2 Beta Download V1.3 driver (opencl driver 1411.4) I have no errors of calculations. Newer I don't use the driver
because on them I can't lower videocard frequency, only dispersal is available that doesn't suit me. I think that all problems on new videocards are connected with OpenCL 2.0
RE: So we know running 2 x
)
Back in July when SETI ran out of work, my cards fell over to running both Einstein and MilkyWay at the same time on the cards. Never had any issues when running SETI and Einstein or SETI and MW at the same time on the same card. Evidently both Einstein and MW fight for contention of the OpenCL resources when run concurrently on the same card since I then produced errors on both projects. I had invalids on both projects and things returned to normal when SETI came back online and my normal mix of work resumed. I posted the errors over at MW in Message 63838.
RE: I'm also not entirely
)
I setup a 'Bonaire' card recently. It's more recent than the 7790 - an R7 260X 2GB. My understanding (and it could be wrong) is that it's the same chip with more memory and at somewhat higher clocks. It also has a factory overclock. A local computer store had them on special so I decided to test one out.
I ran it at 2x, 3x and 4x but had some validate errors at 4x with no gain in performance. After deciding on 3x, and after the weather warmed significantly, it started producing some invalid results (~10%) so I downclocked both core and mem from 1175/1625 MHz to 1150/1600 MHz. That has seemed to get rid of the invalids for the moment. With even warmer weather on the way, I might reduce these a bit more.
So, I'm not seeing this 'concurrent tasks' problem with my particular 'Bonaire'.
Cheers,
Gary.
Since getting my R9 390 I've
)
Since getting my R9 390 I've had it pointed out to me that I've got quite a number of invalids. (Card installed 09/10/15) That was running 2 WU's at a time (Setting 0.5 in preferences)
I'm trying 1 at a time now but that's going to be painfully slow.