perf: optimize find_all_tags_for with caching and indexing #127
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
This is a backport of the changes made in #126
This PR introduces optimizations to the
find_all_tags_for
method and related functionality to improve performance when working with large datasets in theTag
model. Specifically:Caching for
ContentType
Lookups:ContentType
objects for frequently used model names. This reduces redundant database queries forContentType.objects.get()
, especially in high-traffic scenarios or repeated calls.Database Indexes:
target_type
andtarget_object_id
fields in theTag
model.target_type
andtarget_object_id
, particularly in thefind_all_tags_for
method.Optimized Query Logic:
list()
call ontarget.values_list("id", flat=True)
in thefind_all_tags_for
method.Why These Changes Were Made
find_all_tags_for
method was identified as a performance bottleneck, particularly for large datasets in theTag
table (~6 million records).ContentType
lookups were causing unnecessary database queries.target_type
andtarget_object_id
lacked an index, leading to slower performance on large datasets.