On my original topic, I was suspecting that the performance issues I encounter was related to the hub, but after doing further testing, I can say I was wrong about that.
I’ve deployed a fresh MacOS virtual machine and installed only Atuin on it, and didn’t log in to my hub account throughout the whole test . With the “Welcome” runbook on it, everything ran smoothly and the memory utilization of tauri was around 300 MB. But as soon as I move one of my .atrb file to the Atuin Runbooks directory, tauri process started using ~3 GB memory and Atuin Desktop App started to stutter; responding to the clicks very late and only drawing the contents of runbook for after a long delay.
v0.0.105 is currently building and will be out for release very soon. The runbook you shared no longer causes a slowdown
Thanks again!
Edit:
Some fun background; this was because of our search indexer! You had one super long token, and we’d configured it to support prefix fuzzy searching for all content. Usually fine, but for long tokens it results in far too much in the index. Switched to fuzzy prefix on titles only, and otherwise slightly more strict matching on the content.