aboutsummaryrefslogtreecommitdiffstats
path: root/flake.lock
diff options
context:
space:
mode:
authorEllie Huxtable <ellie@elliehuxtable.com>2024-04-25 10:42:04 +0100
committerGitHub <noreply@github.com>2024-04-25 10:42:04 +0100
commitfc5522f45ef0735fb3b492329f95770203d21a7f (patch)
tree34d2ed441561e0387bef0079e238b5a8d629c731 /flake.lock
parentfeat(dotfiles): support syncing shell/env vars (#1977) (diff)
downloadatuin-fc5522f45ef0735fb3b492329f95770203d21a7f.zip
chore: add some more debug logs (#1979)
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.
Diffstat (limited to 'flake.lock')
0 files changed, 0 insertions, 0 deletions