fix(workflow_engine): Add a cache for Workflows to reduce DB load #106925
+76
−16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…che if a relationship to the detector or environment changes.
github-actions
bot
added
the
Scope: Backend
saponifi3d
commented
Jan 23, 2026
|
|
||
| if workflows is None: | ||
| environment_filter = ( | ||
| (Q(environment_id=None) | Q(environment_id=environment.id)) |
Contributor
Author
There was a problem hiding this comment.
🤔 -- this line from the original query will likely cause our cache size to be a lot larger than needed. we could normalize this by having the "env filter = None" results as 1 cached query, and by environment as another.
Would like to see the impact of this / the size of the cache before diving into changing functionality of this query though.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We select workflows from the DB very frequently. This has added substantial load to our DB, even though the query is very fast / efficient.
This PR introduces a caching layer for this high frequency db query.