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.
P99 is usually <100ms which is excellent, but occasionally has big spikes to 1000ms. This is only on the record index.
I don't want this to get out of hand. I've ran a few test queries and they all complete very fast, and are purely index scans.
Hopefully this helps figure out if it's a specific user with tonnes of stores or something? Otherwise there could be something up with my db.
I should probably also figure out some proper log levels or tracing lol.
Checks