So wanted to put a little more data behind the ARS vs Native AD.
- Dataset base on 30 compartmentalized runs of the snippets
- Time based on total seconds and then averaged
Test scenario 1: Search for a specific user in Domain Y.
Native get-aduser |
ARS get-qaduser |
ARS DirectoryEntry EDMS:// |
0.40 |
1.34 |
0.18 |
Test scenario 2: Search for a specific user in Domain X.
Native get-aduser |
ARS get-qaduser |
ARS DirectoryEntry EDMS:// |
0.48 |
1.32 |
0.14 |
Test scenario 3: Search for a specific user in Domain Z.
Native get-aduser |
ARS get-qaduser |
ARS DirectoryEntry EDMS:// |
Cannot from primary |
1.36 |
0.19 |
Test scenario 3: change description for a specific user in Domain X
Native get-aduser |
ARS get-qaduser |
ARS DirectoryEntry EDMS:// |
0.52 |
3.68 |
0.38 |
The ARS cmdlets are heavy. This means that while get-aduser returns 11 attributes the ARS cmdlet returns 33. With the use of EDMS (ADSI calls for ARS the times can be greatly cut). So what is the consensus on this bloat? I have read a few posts and KBs, Talks about setting the datatypes, limiting searches etc.
**Side note on limiting search; the use of -DontUseDefaultIncludedProperties actually causes the cmdlet to run longer...
1.48 with 'DontUseDefaultIncludedProperties'
1.41 WITHOUT 'DontUseDefaultIncludedProperties'