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

v3.6 database migration logic is inefficient for large numbers of device types #8606

New Issue
Closed
opened 2025-12-29 20:38:49 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:38:49 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Sep 12, 2023).

Originally assigned to: @arthanson, @jeremystretch on GitHub.

NetBox version

v3.6.1

Python version

3.8

Steps to Reproduce

This is an extension to bug #13605, which was addressed for device and virtual machines during the v3.6 beta testing period. The issue described therein impacts device types as well, as raised in discussion #13676.

Expected Behavior

Schema migrations should apply without error, and should not consume excessive disk space or memory.

Observed Behavior

Attempting to upgrade to v3.6.0 or later with a large number of device types (over 3,000 as tested) can trigger excessive disk space utilization due to inefficiencies in the component template count logic.

We should be able to resolve this in a manner similar to the fix for #13605.

Originally created by @jeremystretch on GitHub (Sep 12, 2023). Originally assigned to: @arthanson, @jeremystretch on GitHub. ### NetBox version v3.6.1 ### Python version 3.8 ### Steps to Reproduce This is an extension to bug #13605, which was addressed for device and virtual machines during the v3.6 beta testing period. The issue described therein impacts device types as well, as raised in discussion #13676. ### Expected Behavior Schema migrations should apply without error, and should not consume excessive disk space or memory. ### Observed Behavior Attempting to upgrade to v3.6.0 or later with a large number of device types (over 3,000 as tested) can trigger excessive disk space utilization due to inefficiencies in the component template count logic. We should be able to resolve this in a manner similar to the fix for #13605.
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 20:38:49 +01:00
adam closed this issue 2025-12-29 20:38:50 +01:00
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: medium 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#8606
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?