Hello all,
before opening an SR for this I was wondering if anybody else experienced this, as per subject I have a bunch of scripts performing updates on the users in bulk (it can be anything from 30 to 1000+ users) no workflows or anything attached just "one time scripts" required from time to time and whenever I use the Set-QadUser -Identity $something -objectAttributes $myhash -Proxy CPU on the server running the admin services spikes up to 80/90/100% usage and stays that way even long after the script has done running, same goes the consumed memory.
Keep in mind the above is just an example I can update 1 or 10 attributes and result is the same, server has 8 CPUs and 16gb Memory which is fine most of the time apart from when I perform such bulk changes, keep in mind this seems to affect only changes on Virtual Attributes as I perform bulk updates on native AD attributes there is no such performance hiccup.
Do I have a way to reduce cmdlets footprint? Anybody else faced a similar issue? As I said before filing an SR I would like to hear other admins experiences as well.
Thanks in advance for any pointer/help.