Check / Optimize REST Queries #7536

Closed
opened 2025-12-29 20:24:51 +01:00 by adam · 2 comments
Owner

Originally created by @arthanson on GitHub (Jan 20, 2023).

Proposed Changes

Took a look around on our REST queries as a comment came up about the python API being slow, spot check showed a lot of low-hanging optimizations that could be done on the NetBox side:

Cable API: 187 queries
Module Bay: 44 queries
Power Port: 174 queries
vlan group: 23 queries
vlan: 65 queries

Justification

These are not with huge datasets so the larger the dataset the more queries and slower any API calls will be.

Originally created by @arthanson on GitHub (Jan 20, 2023). ### Proposed Changes Took a look around on our REST queries as a comment came up about the python API being slow, spot check showed a lot of low-hanging optimizations that could be done on the NetBox side: Cable API: 187 queries Module Bay: 44 queries Power Port: 174 queries vlan group: 23 queries vlan: 65 queries ### Justification These are not with huge datasets so the larger the dataset the more queries and slower any API calls will be.
adam added the pending closuretype: housekeeping labels 2025-12-29 20:24:51 +01:00
adam closed this issue 2025-12-29 20:24:51 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Apr 20, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 20, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (May 21, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (May 21, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7536