Quote from: Raistmer on 01 Jan 2012, 06:12:30 pmWell, in existing apps I relied on OS/driver to cleanup GPU state when process terminated.It's possible that new AMD drivers can't cleanup properly and need help from application.So I will not go further in optimization and implement full OpenCL objects cleanup inside app instead. Maybe this could help with this issue.Probably that'll be along the right lines. Similar (with slighlty different symptoms) was originally happening under Cuda, resolved by making sure safe exit shutdown code was used, rather than terminating the process/thread during mid kernel execution or memory transfers. The side effects on Cuda devices/drivers were more along the lines of sending the driver into failsafe/sticky-downclock, but I can see that similar mechanisms might result in resource leaks or other unpredictable problems like that.Jason
Well, in existing apps I relied on OS/driver to cleanup GPU state when process terminated.It's possible that new AMD drivers can't cleanup properly and need help from application.So I will not go further in optimization and implement full OpenCL objects cleanup inside app instead. Maybe this could help with this issue.
One ATI_r521 AP task running slowly, then GPUs suspended and resummedClaggy
well, many hours running in 3 tasks config already - no GPUload drop.Always ~99%.For some reasons x1 and x2 configs unstable and x3 stable? Very strange...Well, when I plot graphs it will be more clear if elapsed time deviation reduced too in x3 config or just GPU load improved for some of 3 tasks and not for some others...
So, this issue is common for both drivers.What about -hp switch in menchmark command line? Does it helps ?
I don't know about such windows updates.PErformance drop was reported more than month ago, bug was confirmed... and no more info from NV side.