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

circuits.* excluded from Cacheops #2971

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

Originally created by @sdktr on GitHub (Oct 24, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.6.6

Steps to Reproduce

  1. Fresh install of Netbox 2.6.6
  2. Stresstest a single resource under the /circuits/ app (e.g /api/circuits/circuit/123/
  3. Notice DB-related respones and no queries to redis

Expected Behavior

Circuits should fetch from cache as the other apps are configured to do

Observed Behavior

Circuits are limited in DB throughput and don't benefit from lower latency that the cache provides

Cause

Circuits app is not in the cacheops config
ae4f17264f/netbox/netbox/settings.py (L363)

Originally created by @sdktr on GitHub (Oct 24, 2019). <!-- NOTE: This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.6.6 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox (or the current beta release where applicable). Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a wrapper like pynetbox. --> ### Steps to Reproduce 1. Fresh install of Netbox 2.6.6 2. Stresstest a single resource under the /circuits/ app (e.g /api/circuits/circuit/123/ 3. Notice DB-related respones and no queries to redis <!-- What did you expect to happen? --> ### Expected Behavior Circuits should fetch from cache as the other apps are configured to do <!-- What happened instead? --> ### Observed Behavior Circuits are limited in DB throughput and don't benefit from lower latency that the cache provides ### Cause Circuits app is not in the cacheops config https://github.com/netbox-community/netbox/blob/ae4f17264fcc2a3d3ef7f9bf81a9e1d8ce88878d/netbox/netbox/settings.py#L363
adam added the type: bugstatus: accepted labels 2025-12-29 18:24:15 +01:00
adam closed this issue 2025-12-29 18:24:15 +01:00
adam commented 2025-12-29 18:24:16 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Oct 24, 2019):

Should we change cacheops config to include *.* and only specify the exceptions ? Same way as auth is setup currently?

EDIT: not recommended by cacheops per their own documentation:

Using '.' with non-empty ops is not recommended since it will easily cache something you don't intent to or even now about like migrations tables. The better approach will be restricting by app with 'app_name.*'. (https://github.com/Suor/django-cacheops)

@sdktr commented on GitHub (Oct 24, 2019): Should we change cacheops config to include `*.*` and only specify the exceptions ? Same way as `auth` is setup currently? EDIT: not recommended by cacheops per their own documentation: > Using '*.*' with non-empty ops is not recommended since it will easily cache something you don't intent to or even now about like migrations tables. The better approach will be restricting by app with 'app_name.*'. (https://github.com/Suor/django-cacheops)
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: 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#2971
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?