CLI Slow Start?

[binduwavell]

This may very well be an issue in my environment, I'm curious why td --version takes over 5 seconds to complete:

~/dist> time td --version
td version 0.37.0
td --version  0.04s user 0.03s system 1% cpu 5.371 total

If you can't reproduce this issue, I have no problem with closing this. If you need me to provide any other info, I'm happy to do so. Grabbing --version from most CLIs complete "instantly". I'm running in an Ubuntu WSL on Windows 11. I have 64G RAM and 8 fast cores. Machine is a high end dev laptop from about 2 years ago.

[marcus]

Hey @binduwavell — thanks for reporting this. Can't reproduce on my end (~77ms for td --version), but I have a theory.

Do you have td sync enabled? (td config get sync.autosync) td runs a sync hook on every command startup, and if the sync server is unreachable or slow, it could block for several seconds waiting on a network timeout. On WSL, network latency to external services can be higher than expected.

A quick test: try td features disable sync.autosync (or td config set sync.url "") and see if --version drops back to instant. If so, we should make the startup sync non-blocking so it doesn't stall simple commands like --version.

Let me know what you find!

[binduwavell]

Thank you for your suggestions. I just installed td binary and did not configure anything. I did run td init in a project to see what it would do, but when I was running it I was not in a td managed project. Is on my work machine, will give the config change a shot when I'm back in the office. I'm not sure what td sync even is :)

[marcus]

Sounds good, @binduwavell — no rush! When you get a chance, the config to check is td config get sync.autosync. If it's enabled and the sync server isn't reachable from your work machine, that's likely the culprit. Let us know what you find and we'll go from there. ✦