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

N+1 problem in dcim/ipam API calls #11081

New Issue
Closed
opened 2025-12-29 21:40:00 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:40:00 +01:00
Owner
Copy Link

Originally created by @Tishka17 on GitHub (Apr 24, 2025).

Originally assigned to: @Tishka17 on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.2.8

Python Version

3.10

Steps to Reproduce

  1. Enable SQL logging
  2. Do API requests:
  • api/ipam/ip-addresses/
  • api/ipam/prefixes
  • api/dcim/interfaces

Expected Behavior

All required data is loaded by batch SQL requests

Observed Behavior

In the output you will see repeated SQL calls for each object in the response set:

  • circuits_virtualcircuittermination for interfaces
  • dcim_interface folowing by dcim_device for ip-address
  • dcim_site for prefixes
Originally created by @Tishka17 on GitHub (Apr 24, 2025). Originally assigned to: @Tishka17 on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.2.8 ### Python Version 3.10 ### Steps to Reproduce 1. Enable SQL logging 2. Do API requests: * api/ipam/ip-addresses/ * api/ipam/prefixes * api/dcim/interfaces ### Expected Behavior All required data is loaded by batch SQL requests ### Observed Behavior In the output you will see repeated SQL calls for each object in the response set: * `circuits_virtualcircuittermination` for interfaces * `dcim_interface` folowing by `dcim_device` for ip-address * `dcim_site` for prefixes
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:40:00 +01:00
adam closed this issue 2025-12-29 21:40:00 +01:00
adam commented 2025-12-29 21:40:01 +01:00
Author
Owner
Copy Link

@Tishka17 commented on GitHub (Apr 24, 2025):

I understand that PR was not recommended to create, but I needed these changes to validate my hypotesis.

@Tishka17 commented on GitHub (Apr 24, 2025): I understand that PR was not recommended to create, but I needed these changes to validate my hypotesis.
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 severity: low status: accepted type: bug
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#11081
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?