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

Document best practices for ensuring optimal performance in NetBox #11629

New Issue
Closed
opened 2025-12-29 21:47:50 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:47:50 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Sep 17, 2025).

Originally assigned to: @jeremystretch on GitHub.

Change Type

Addition

Area

Other

Proposed Changes

Add a new section detailing performance considerations and tips to the NetBox "best practices" documentation. Some topics include:

  • Provisioning an adequate number of WSGI worker processes
  • Setting sane pagination limits
  • Segmenting background jobs into different queues
  • Crafting performant REST API requests (e.g. brief=True and fields=…)
  • Explaining that GraphQL is not, in fact, magic
Originally created by @jeremystretch on GitHub (Sep 17, 2025). Originally assigned to: @jeremystretch on GitHub. ### Change Type Addition ### Area Other ### Proposed Changes Add a new section detailing performance considerations and tips to the NetBox "best practices" documentation. Some topics include: * Provisioning an adequate number of WSGI worker processes * Setting sane pagination limits * Segmenting background jobs into different queues * Crafting performant REST API requests (e.g. `brief=True` and `fields=…`) * Explaining that GraphQL is not, in fact, magic
adam added the status: acceptedtype: documentation labels 2025-12-29 21:47:50 +01:00
adam closed this issue 2025-12-29 21:47: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 status: accepted type: documentation
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#11629
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?