Atuin runs extremely laggy after logging in to the hub

I’ve been observing extreme lags while using Atuin Desktop lately. This lagginess includes:

  • Creating / Selecting workspaces, runbooks
  • Navigating through the page and/or any line of code
  • Running single scripts or a complete runbook
  • Switching between organizations

This lagginess is not only observable when switched to an organization which I’m a member of, but also when using a local only workspace.

To test further, I’ve installed a fresh MacOS on a VM and set up Atuin Desktop.

It was running vey smoothly until I’ve logged into the hub. As soon as the logging in is complete, the unresponsiveness begun. I even tried to log out from the hub, quit the application and re-open it to see if it helped, but no joy. It only becomes fluid again if you completely remove it and re-install.

There is a process called tauri://localhost that consumes nearly as %100 of CPU constantly when this happens.

Please let me know if there is a fix since it’s not possible for me to use it anymore.

Note: All tests were ran on 0.0.95 (20250912.172946)

We have a suspicion this is due to background syncing, although the fact that it continued after you logged out and restarted is interesting.

The next update will include a setting to completely disable background syncing of runbooks, as well as a setting to control how many runbooks sync at once. I’ll post here again once it’s released.

1 Like

This has been released in 0.0.97 and can be found in the General section of the settings pane. It defaults to background sync being off, so hopefully you should see an improvement right away.

1 Like

I did not have any problems with previous versions and the new version seems to run fine, too.

Only the new setting does not work:

On Debian via WSL, the background sync setting does not do anything.

The behavior is exactly the same as before, which is fine for me.

The behaviour is probably not something you would notice, per-say

Background sync on

This syncs both the online workspace contents in the background (file tree, etc) AND the contents of the runbooks themselves.

Background sync off

This still syncs the file tree, but runbook contents will not be synced in the background. They will update once opened.

So unless you’re regularly switching between online/offline and expect things to be as up-to-date as possible, you likely won’t notice much difference

2 Likes

Thanks for the clarification.

1 Like

Thanks for the quick update @BinaryMuse !

0.0.97 significantly improved the overall speed and made Atuin Desktop usable for me. But still, it feels very sluggish when navigating and this gives the impression of its utilizing too much resources for what it actually does (just browsing through runbooks/workspaces/organizations).

I’m watching tauri process’ CPU utilization as I use it and it frequently goes up to ~%95. I’m dreaming of Atuin Desktop to be as responsive as using Joplin, what cool it would be :sweat_smile: