starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

API call to Interfaces seems slow #1934

New Issue
Closed
opened 2025-12-29 17:20:41 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:20:41 +01:00
Owner
Copy Link

Originally created by @mw-0 on GitHub (Aug 13, 2018).

Environment

  • Python version: 3.4.8
  • NetBox version: 2.3.4

Steps to Reproduce

Call the api endpoint
time curl http://netbox/api/dcim/interfaces/?limit=100

Expected Behavior

Data returned is ok but i would expect it to be far quicker based on data size.

Observed Behavior

When checking times for the API i can see the calls to api/dcim/interfaces/ seem slow.

When i call /api/dcim/interfaces/?limit=100 it takes 4.5sec

Comparing this to /api/dcim/devices/?limit=100 it takes 1.3s

If i compare the amount of data returned devices shows over double the content for the call as well. I have seen a ticket that sped up the devices call closed and was wondering if interfaces could also be helped.

Originally created by @mw-0 on GitHub (Aug 13, 2018). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.4.8 * NetBox version: 2.3.4 ### Steps to Reproduce Call the api endpoint time curl http://netbox/api/dcim/interfaces/?limit=100 ### Expected Behavior Data returned is ok but i would expect it to be far quicker based on data size. ### Observed Behavior When checking times for the API i can see the calls to api/dcim/interfaces/ seem slow. When i call /api/dcim/interfaces/?limit=100 it takes 4.5sec Comparing this to /api/dcim/devices/?limit=100 it takes 1.3s If i compare the amount of data returned devices shows over double the content for the call as well. I have seen a ticket that sped up the devices call closed and was wondering if interfaces could also be helped.
adam closed this issue 2025-12-29 17:20:41 +01:00
adam commented 2025-12-29 17:20:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 15, 2018):

Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided here. This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!

@jeremystretch commented on GitHub (Aug 15, 2018): Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/tree/develop/.github/ISSUE_TEMPLATE). This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!
adam commented 2025-12-29 17:20:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 22, 2018):

i would expect it to be far quicker

This isn't an actionable statement. Like every application, NetBox's performance is dependent largely upon the environment in which is runs. If you can identify specific opportunities for performance improvement I'll be happy to look into them.

@jeremystretch commented on GitHub (Aug 22, 2018): > i would expect it to be far quicker This isn't an actionable statement. Like every application, NetBox's performance is dependent largely upon the environment in which is runs. If you can identify specific opportunities for performance improvement I'll be happy to look into them.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1934
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?