question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

/api/v3/me endpoint is painfully slow

See original GitHub issue

Context

When entering carto.com, loading the Dashboard information is really slow. With my team account, the api/v3/me endpoint takes ~1.5 seconds to load.

Additional info

Checking the load times in Kibana you can see load times of up to 5 seconds and you can see that team accounts take more or less the same time, so the load time might grow with the team size (unchecked supposition).

@ramiroaznar Can you check if this can be added to RT, please?

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:14 (11 by maintainers)

github_iconTop GitHub Comments

2reactions
juanignacioslcommented, May 15, 2018
1reaction
javitoninocommented, Aug 20, 2018

That would alleviate the problem a lot since the dashboard is a more common entry point than for instance the account page.

Just doing that won’t alleviate the problem without more changes. We cannot remove it from that endpoint since itr’s used in other parts of the frontend, and that endpoint must contain anything that is needed for frontend (since it’s the only way front statics know how to get information from backend). So, even if it’s used only in profile pages, we still need it in that endpoint. Also, in the dashboard, there is also (at least) the enable/disabled import button, so that dropdown is not the only place.

We would have to remove or change all usages of that from the frontend before we can remove it from that endpoint. My point is that it’s probably not such a quick fix as it looks like.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Best Practices to avoiding slow API response time
There are a few optimizations that you can do to avoid slow API responses: Increasing the number of records returned per page.
Read more >
8 reasons why your API adoption is so slow - TechBeacon
1. Documentation has bad design · 2. API provider didn't consider the developer experience · 3. API provider didn't lead the developer community...
Read more >
How to Deal With Slow APIs - DZone
A better approach, in this case, is to not deal with the response coming out of a slow API but to simply stop...
Read more >
API calls are very slow. Combining multiple requests? - GitLab
Combining multiple requests? I'm working on an automatic Kanban board for GitLab, and it provides a GraphQL syntax that use GitLab API.
Read more >
API Docs swagger is very slow · Issue #6645 - GitHub
Issue seems isolated to any endpoint that return a large document. Which is basically all of them.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found