Skip to main content
Question

MVIS fine tuning v2.3.0

  • December 24, 2025
  • 0 replies
  • 6 views

Junaid Dada

Hi, Does anyone have some advise on how to optimise / fine tune MVIS response times on APIs given some latency when using OAuth?

When changing the Http Auth type from basic (or even digest) to OAuth, I find my the response times on APIs increases significantly (as expected due to the additional token validation using the JWKS URL).

I have response times using basic auth +-50ms going up to +-500ms on Oauth. Any idea if there are ways to cache the tokens on MVIS or other ways to fine tune this? The only solution we have for now is to bump up connection pools to increase capacity which is not that sustainable as we add more APIs to the server going forward. I have also played around with increasing timeouts and other config parameters on server and account level to delay failures on load. 

Or maybe something to consider for future in MVIS?

Im using AzureAD as the Oauth provider.