Hello,
We have a Large RDS platform, which includes over 500 collections on server 2016, after publishing 5 applications to 150 of the collections we are now getting slow response times via power shell ie Get-RDSessionCollection. Is there a limit to the total number of published applications this does not appear to be documented anywhere?
Operationally the connection brokers plus SQL appear fine memory, disk cpu.
We are planning to roll out the applications to remaining collection shortly apart from a slow response via powershell we have no other problems apart from the power shell slowness.
Thanks
We have a Large RDS platform, which includes over 500 collections on server 2016, after publishing 5 applications to 150 of the collections we are now getting slow response times via power shell ie Get-RDSessionCollection. Is there a limit to the total number of published applications this does not appear to be documented anywhere?
Operationally the connection brokers plus SQL appear fine memory, disk cpu.
We are planning to roll out the applications to remaining collection shortly apart from a slow response via powershell we have no other problems apart from the power shell slowness.
Thanks