Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Very slow CLI and possible cancelled call bugs on Windows
Hi,
This has been raised a few times in the past which I've seen and so let it be as it was always replied to suggesting that it was being actively worked on. But performance of the CLI on Windows...
Sorry for the repeated posts (and the iffy formatting - the UI buttons don't give the full range of what appear to be Markdown options) ... just had the idea to run on WSL2 on the same machine. Using my legacy version v2.4 it was consistently in the 2.1-2.5s range. Still slow but half the time of Windows.
Notably, I could not replicate the Ctrl-C behaviour from Windows so it seems like it's skipping that first ~2.6s execution altogether.
Upgrading to 2.13.1 the performance is much worse for non-cached (both the first entry and when running with --cached=false), and much better for cached results. It was in the 3.1-3.5s range for non-cached results, but ~1.3s for cached after the first run.
real 0m1.331s
user 0m0.145s
sys 0m0.094s
Honestly, that's still really slow for a local, cached, CLI, but I'd kill for that on Windows compared to >5s.
