I've had trouble following this technical conversation but I've basically aborted my BRP6 1.52 work units.
The GPU load was 0% and showing a ridiculous amount of time remaining to complete. I assume there's an issue with 1.52.
There's no issue with 1.52. The new 1.54 app that is being tested is for people with NVIDIA GPUs so that they can take advantage of possible performance improvements coming from a more recent version of the cuda libs. With your AMD GPU this is of no relevance to you.
Performance on your particular model should already be very good. The wide range of completion times for BRP6 tasks showing in your tasks list indicates that there is something sub-optimal with your system. The News thread is not the place to discuss this. Please start a new thread on the "Problems" board giving the details of your setup - particularly (but not limited to) things like the mix of CPU and GPU tasks you run and how many concurrent GPU tasks and the number of "free" CPU cores you have to support GPU tasks. You are active at a number of projects. Details about resource shares and the other apps that you run should also be given.
You previously had 1.53 tasks that all errored almost immediately. You wont have any of those left but there WILL be parts in your state file that still refer to the 1.53 app. You should just ignore those references because there will be current replacements referring to the 1.54 app and all and blocks will have the correct of 154, so nothing to worry about.
Thanks Gary an unrelated restart yesterday, and i checked after reading your post this evening and you are right.... ¨nothing more to see here - move along¨.
Possible problem with an
)
Possible problem with an unresolved dependency on LIBWINPTHREAD-1.DLL
Shouldn't my GTX660 on my W8
)
Shouldn't my GTX660 on my W8 box be receiving CUDA 55 Parks PMS task rather than CUDA32?
RE: Shouldn't my GTX660 on
)
Not while the app has been withdrawn for bugfixing.
Richard thanx, I look forward
)
Richard thanx, I look forward to seeing what the card can do when more of it's capabilities are used.
I've had trouble following
)
I've had trouble following this technical conversation but I've basically aborted my BRP6 1.52 work units.
The GPU load was 0% and showing a ridiculous amount of time remaining to complete. I assume there's an issue with 1.52.
RE: ... I assume there's an
)
There's no issue with 1.52. The new 1.54 app that is being tested is for people with NVIDIA GPUs so that they can take advantage of possible performance improvements coming from a more recent version of the cuda libs. With your AMD GPU this is of no relevance to you.
Performance on your particular model should already be very good. The wide range of completion times for BRP6 tasks showing in your tasks list indicates that there is something sub-optimal with your system. The News thread is not the place to discuss this. Please start a new thread on the "Problems" board giving the details of your setup - particularly (but not limited to) things like the mix of CPU and GPU tasks you run and how many concurrent GPU tasks and the number of "free" CPU cores you have to support GPU tasks. You are active at a number of projects. Details about resource shares and the other apps that you run should also be given.
Cheers,
Gary.
No worries, thanks for the
)
No worries, thanks for the reply Gary!
The version number for BRP6
)
The version number for BRP6 1.54 are reporting as
einsteinbinary_BRP6
153
153
in client_state.xml
I guess that should be 154.
RE: .... in
)
No.
You previously had 1.53 tasks that all errored almost immediately. You wont have any of those left but there WILL be parts in your state file that still refer to the 1.53 app. You should just ignore those references because there will be current replacements referring to the 1.54 app and all and blocks will have the correct of 154, so nothing to worry about.
Cheers,
Gary.
RE: ... so nothing to worry
)
Thanks Gary an unrelated restart yesterday, and i checked after reading your post this evening and you are right.... ¨nothing more to see here - move along¨.