Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android performance issues for token generation #1558

Open
karthik-mut opened this issue Sep 6, 2021 · 2 comments
Open

Android performance issues for token generation #1558

karthik-mut opened this issue Sep 6, 2021 · 2 comments
Assignees
Labels
Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue Performance

Comments

@karthik-mut
Copy link

We are seeing performance issues with the android version of msal library .
But we are not seeing the same issues with the ios devices .
For example: We are seeing the messages in the telemetry as :
Time taken to generate token: 7268ms,
Time taken to generate token: 1744ms,
Time taken to generate token: 10827ms,

The numbers are little bit high with the lower end version of android devices .
Currently we are using 2.0+ Version [ implementation 'com.microsoft.identity.client:msal:2.2.+']
Can you please help us how to resolve this issue ?

@shoatman shoatman self-assigned this Sep 10, 2021
@shoatman shoatman added Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue Performance labels Sep 10, 2021
@shoatman
Copy link
Contributor

The library doesn't generate the token per se. It requests it from the Azure Active Directory v2 endpoint. For performance related inquiries it would be great to have more information about the following:

  • Type of device
  • Network Type/Performance where observed

@karthik-mut
Copy link
Author

Type of Device : Samsung and Oppo with Android 10 and 9 Versions
Network Type : WI-FI
We are observing issues majorly with android 10 devices and the tested devices are samsung and oppo devices .
Can we know what is the expected SLA for acquiring the token or for acquiring the silent token methods ?
We have tested in simulators as well it is taking more than a second but in production with real devices we are seeing 3-5 seconds .
Thank you for the response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue Performance
Projects
None yet
Development

No branches or pull requests

2 participants