It's just a guess, but this looks like an issue collecting domain group members from Active Directory for Orion authentication. I've scoured previous cases, KB articles, and Thwack, and have been unable to find any previous reported cases that are even somewhat related to the symptoms you describe. My recommendation would be to gather Diagnostics and open up a case with support so we can troubleshoot this issue properly. In the meantime though, if this is severally impacting your production environment you can try and disable Active Directory authentication to see if that brings the CPU back down. Be sure to collect the diagnostics before making this change. You may need to restart all Orion services and IIS before the CPU returns to normal levels.
↧