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.

Sign up for GitHub

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

Jump to bottom

Accessing the API is slow when there is a lot of data #1939

Open
hmpf opened this issue May 7, 2019 · 1 comment
Open

Accessing the API is slow when there is a lot of data #1939

hmpf opened this issue May 7, 2019 · 1 comment
Labels
nav-ref Fronted by the NAV user reference committee
Projects
NAV referansegruppe liveboard

Comments

@hmpf
Copy link
Contributor

hmpf commented May 7, 2019

No description provided.

@hmpf hmpf added the nav-ref Fronted by the NAV user reference committee label May 7, 2019
@lunkwill42
Copy link
Member

I believe some of this stems from the fact that some of the API endpoints tend to inline too many of the related objects of each response record. E.g., why does each Interface record need to inline the Netbox object it is attached to? This seems especially silly when using the /interfaces endpoint to list all the interfaces on a single Netbox. If the Netbox has 200 ports, you will return 200 copies of the same Netbox record inlined.

@lunkwill42 lunkwill42 mentioned this issue Dec 1, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
nav-ref Fronted by the NAV user reference committee
Projects
NAV referansegruppe liveboard
To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lunkwill42 @hmpf