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
Fetch response.json() seems slower than response.text() #6418
Comments
@mchev2 Can you do some profiling and post the results? |
I did some independent tests and did not see any difference between res.text and res.json. I had to add in caching so res.text will work for my use case. I'm not sure where the issue could be. Perhaps the json is too heavily nested and so there is a bottleneck. I will close this for now and let you know if I find anything else. Thank you |
@mchev2 just bringing this guy's issue to your attention, could be similar. |
I have encountered the same issue, the responseText comes back straight away in milliseconds, but when it convert to json using .json(), it takes a few seconds, the interesting thing is if I click the screen during the .json() parsing period, it get the json data back straight away |
Make sure you are:
|
Just wanted to document this performance issue (incase it really exists).
The text was updated successfully, but these errors were encountered: