Perf: Investigate optimizations around AcquireTokenSilentSupplier.getAuthorityWithPrefNetworkHost #897
Labels
confidential-client
For issues related to confidential client apps
Enhancement
A request or suggestion to improve some aspect of the library
public-client
For questions/issues related to public client apps
While doing some perf investigations on Azure Identity I noticed that we spend a ton of time in
getAuthorityWithPrefNetworkHost
when getting tokens out of the cache. The perf test is literally callingacquireTokenForManagedIdentity
in a hot loop with no parameters or authority configured.It ends up being ~70% of the time under
AcquireSilentTokenSupplier.execute()
:Discussion with @Avery-Dunn offline leads to the thought that we can optimize this path some - there's no reason to recompute and reconstruct an authority every call.
This should be investigated in the silent, device code, and auth grant flows.
The text was updated successfully, but these errors were encountered: