From c5f74bc466d2038f581a801d7df293255c40d5a8 Mon Sep 17 00:00:00 2001 From: Ilya Grigoriev Date: Thu, 14 Sep 2023 21:23:12 -0700 Subject: [PATCH] docs: mention `git pack-refs` for co-located repos As suggested by @yuja in https://github.com/martinvonz/jj/issues/1841#issuecomment-1720451152 Thanks to @lazywei for pointing out that `git pack-refs --all` is better, at least on the first run. I haven't checked, but suspect, that because of the number of `refs/jj` refs jj creates, it might always be better. --- docs/git-compatibility.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/git-compatibility.md b/docs/git-compatibility.md index 0dde7c146..7720e4faf 100644 --- a/docs/git-compatibility.md +++ b/docs/git-compatibility.md @@ -128,6 +128,11 @@ repos may require you to deal with more involved Jujutsu and Git concepts. it because they automatically run `git fetch` in the background from time to time. +* In co-located repos with a very large number of branches or other refs, `jj` + commands can get noticeably slower because of the automatic `jj git import` + executed on each command. This can be mitigated by occasionally running `git + pack-refs --all` to speed up the import. + * Git tools will have trouble with revisions that contain conflicted files. While `jj` renders these files with conflict markers in the working copy, they are stored in a non-human-readable fashion inside the repo. Git tools will often