Re: Major issue with gpu priorities sos
Posted: Sun Mar 13, 2016 8:51 pm
Hi,
The ETA will be clear once the v3 Standalone moves out of Alpha, as any plugin is dependent on a stable Standalone. The ETA for the standalone is dependent on the outcomes of on-going customer testing. Tentative target dates fall around the late-April mark - again, this is not official, but is the closest to an ETA I'm in a position to give. All v3 plugins should follow on quickly from that point on wards.
As for the performance issue - what I've found on this end is that using multiple GPUs heats up the cards considerably. This is due to an expensive core function being called frequently. This was not an issue in prior plugins, but a lot of additional features has since been layered over the top, exerting an accumulated effect on performance. Making core functions more efficient would call for some refactoring - these efforts are being poured into the v3 iteration of the plugin. At this stage, it is difficult to determine if carrying these efforts over to v2 would be possible - there isn't much more I can say with total certainty beyond that.
When you say that the previous plugin was running smoothly, are you referring to 2.15? If there are settings tweaks or anything else that can be done on your 2.16 version that could minimize the issue you are having, I will look into that for you.
Cheers,
Azen
The ETA will be clear once the v3 Standalone moves out of Alpha, as any plugin is dependent on a stable Standalone. The ETA for the standalone is dependent on the outcomes of on-going customer testing. Tentative target dates fall around the late-April mark - again, this is not official, but is the closest to an ETA I'm in a position to give. All v3 plugins should follow on quickly from that point on wards.
As for the performance issue - what I've found on this end is that using multiple GPUs heats up the cards considerably. This is due to an expensive core function being called frequently. This was not an issue in prior plugins, but a lot of additional features has since been layered over the top, exerting an accumulated effect on performance. Making core functions more efficient would call for some refactoring - these efforts are being poured into the v3 iteration of the plugin. At this stage, it is difficult to determine if carrying these efforts over to v2 would be possible - there isn't much more I can say with total certainty beyond that.
When you say that the previous plugin was running smoothly, are you referring to 2.15? If there are settings tweaks or anything else that can be done on your 2.16 version that could minimize the issue you are having, I will look into that for you.
Cheers,
Azen