perf(aci): Cache Group lookup for process_workflows/trigger_action #99449
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.
For process_workflows_event, querying for Group is one of the primary required queries.
It's frequently very fast (~1ms), but at times we've observed it taking 100ms or more. Perhaps more significantly, querying for Group by ID is the most common query the app does, and we're part of htat.
Given that this task runs after post_process, which does read Group through the cache, the Group we're processing should nearly always be in the cache, so here we expect a very high hit rate, a significant reduction in query volume to the database, and improvement in some of our wost case task latency.