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

Pre-render utilization data for aggregates, prefixes, and IP ranges #5475

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

Originally created by @jeremystretch on GitHub (Oct 5, 2021).

NetBox version

v3.0.5

Feature type

Change to existing functionality

Proposed functionality

This issue seeks to explore the feasibility of pre-rendering and recording utilization data for aggregates, prefixes, and IP ranges in the database. Currently, when retrieving a list of prefixes, NetBox will calculate the utilization of each on-demand. As an alternative implementation, we could store these values directly on each object in the database, and update them appropriately as child objects are created and deleted.

Use case

This would greatly improve performance where utilization data is required. It would also enable us to easily return this information via the REST API as proposed in #7292.

Database changes

Addition of a utilization decimal field on each of the affected models

External dependencies

No response

Originally created by @jeremystretch on GitHub (Oct 5, 2021). ### NetBox version v3.0.5 ### Feature type Change to existing functionality ### Proposed functionality This issue seeks to explore the feasibility of pre-rendering and recording utilization data for aggregates, prefixes, and IP ranges in the database. Currently, when retrieving a list of prefixes, NetBox will calculate the utilization of each on-demand. As an alternative implementation, we could store these values directly on each object in the database, and update them appropriately as child objects are created and deleted. ### Use case This would greatly improve performance where utilization data is required. It would also enable us to easily return this information via the REST API as proposed in #7292. ### Database changes Addition of a `utilization` decimal field on each of the affected models ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:28:28 +01:00
adam closed this issue 2025-12-29 19:28:28 +01:00
adam commented 2025-12-29 19:28:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 8, 2021):

Ditching this idea in favor of #7845.

@jeremystretch commented on GitHub (Dec 8, 2021): Ditching this idea in favor of #7845.
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 type: feature
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#5475
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?