Limit the frequency of working copy snapshots?

[sourcefrog]

I love the way jj makes frequent easily accessible snapshots of the working copy.

However, I'm trying it out in a very large tree (~300k files) where checking the tree state takes a couple of seconds. For reasons I've not yet tracked down, watchman does not seem to work properly: it doesn't reliably see updates.

In particular it's a bit annoying if I run jj st, jj diff, jj log and each of them insists on checking the whole tree. Or jj b l I think doesn't do anything with the working copy, but still spends time taking one.

I guess I could configure log through an alias to ignore the working copy.

I had another idea, though I'm not sure it's a good one. That is: if the tree is large, the working copy state is allowed to be a little stale for commands like "log" that don't strictly need a fresh copy. Perhaps: if the tree was last checked <5s ago and the last check took >200ms then act as if --ignore-working-copy was set. (Or, perhaps I should just work out what's up with watchman.)

[martinvonz]

Or, perhaps I should just work out what's up with watchman.

+1 :) I think that's the cleanest solution.