Add index to improve performance of fact deletion #5905
Merged
+42
−0
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.

Hey, I just made a Pull Request!
I saw that the highest load on my backstage DB by far was from the following query:
Which is run as part of the fact generation here.
The performance of this query is very slow for a database with a large number of entities or a large history of facts. We could see somewhat better performance by reducing the number of entities or facts per entity, but adding an index would really help.
There is currently an index on



['id', 'entity', 'timestamp']but not on['id', 'timestamp']. Adding this index significantly reduces the load on the DB and the overall performance of the tech insights plugin. Here are my DB metrics from when the index was added:✔️ Checklist
Signed-off-byline in the message. (more info)