Hi,
Has anyone seen performance issues when using the Quest cmdlets? For example, comparing the execution of get-aduser and get-qaduser yielded the following results when scoped to a specific OU containing about 4,500 users:
Native: Get-ADUser
Measure-command -Expression {Get-ADUser -SearchBase 'OU DN Path' -SearchScope Subtree -Filter *} | Select TotalSeconds
TotalSeconds : 15.3429789
QAD Cmdlet to AD:
Measure-command -Expression {Get-QADUser -SearchRoot 'OU DN Path' -SearchScope Subtree -SizeLimit 0} | Select TotalSeconds
TotalSeconds : 145.1344522
QAD Cmdlet to ARS Provider (Proxy specified):
Measure-command -Expression {Get-QADUser -SearchRoot 'OU DN Path' -SearchScope Subtree -SizeLimit 0 -Proxy} | Select TotalSeconds
TotalSeconds : 199.606666
We've also seen extremely poor performance in workflows within ARS that contained search operations as well as running QAD cmdlets that perform an update operation.
Thanks!