From: Victoria Dye <vdye@github•com>
To: Shuqi Liang <cheskaqiqi@gmail•com>, git@vger•kernel.org
Cc: gitster@pobox•com, derrickstolee@github•com
Subject: Re: [PATCH v4] write-tree: integrate with sparse index
Date: Fri, 21 Apr 2023 14:42:34 -0700 [thread overview]
Message-ID: <8b2a754c-6162-54d9-e9ba-fd994058066c@github.com> (raw)
In-Reply-To: <20230421004108.32554-1-cheskaqiqi@gmail.com>
Shuqi Liang wrote:
> Update 'git write-tree' to allow using the sparse-index in memory
> without expanding to a full one.
>
> The recursive algorithm for update_one() was already updated in 2de37c5
> (cache-tree: integrate with sparse directory entries, 2021-03-03) to
> handle sparse directory entries in the index. Hence we can just set the
> requires-full-index to false for "write-tree".
>
> The `p2000` tests demonstrate a ~96% execution time reduction for 'git
> write-tree' using a sparse index:
>
> Test before after
> -----------------------------------------------------------------
> 2000.78: git write-tree (full-v3) 0.34 0.33 -2.9%
> 2000.79: git write-tree (full-v4) 0.32 0.30 -6.3%
> 2000.80: git write-tree (sparse-v3) 0.47 0.02 -95.8%
> 2000.81: git write-tree (sparse-v4) 0.45 0.02 -95.6%
Please update your commit message to explain only the incremental updates on
top of 1a65b41b38a (write-tree: integrate with sparse index, 2023-04-03);
that patch's message (what you have here) does not accurately describe what
_this_ patch is doing.
> diff --git a/builtin/write-tree.c b/builtin/write-tree.c
> index 32e302a813..a9d5c20cde 100644
> --- a/builtin/write-tree.c
> +++ b/builtin/write-tree.c
> @@ -38,12 +38,15 @@ int cmd_write_tree(int argc, const char **argv, const char *cmd_prefix)
> };
>
> git_config(git_default_config, NULL);
> +
> + if (the_repository->gitdir) {
> + prepare_repo_settings(the_repository);
> + the_repository->settings.command_requires_full_index = 0;
> + }
> +
> argc = parse_options(argc, argv, cmd_prefix, write_tree_options,
> write_tree_usage, 0);
>
> - prepare_repo_settings(the_repository);
> - the_repository->settings.command_requires_full_index = 0;
> -
What is the functional benefit of this change? AFAICT, we don't need
'command_requires_full_index' to be set before 'parse_options' in this case,
so this won't have any effect on the behavior of 'write-tree'.
> diff --git a/t/t1092-sparse-checkout-compatibility.sh b/t/t1092-sparse-checkout-compatibility.sh
> index 9bbc0d646b..d3eb31326b 100755
> --- a/t/t1092-sparse-checkout-compatibility.sh
> +++ b/t/t1092-sparse-checkout-compatibility.sh
> @@ -2055,22 +2055,32 @@ test_expect_success 'grep sparse directory within submodules' '
> test_cmp actual expect
> '
>
> -test_expect_success 'write-tree on all' '
> +test_expect_success 'write-tree' '
> init_repos &&
>
> + test_all_match git write-tree &&
> +
> write_script edit-contents <<-\EOF &&
> echo text >>"$1"
> EOF
>
> + # make a change inside the sparse cone
> run_on_all ../edit-contents deep/a &&
> - run_on_all git update-index deep/a &&
> + test_all_match git update-index deep/a &&
> test_all_match git write-tree &&
> + test_all_match git status --porcelain=v2 &&
>
> + # make a change outside the sparse cone
> run_on_all mkdir -p folder1 &&
> run_on_all cp a folder1/a &&
> run_on_all ../edit-contents folder1/a &&
> - run_on_all git update-index folder1/a &&
> - test_all_match git write-tree
> + test_all_match git update-index folder1/a &&
> + test_all_match git write-tree &&
> + test_all_match git status --porcelain=v2 &&
> +
> + # check that SKIP_WORKTREE files are not materialized
> + test_path_is_missing sparse-checkout/folder2/a &&
> + test_path_is_missing sparse-index/folder2/a
Test updates look good!
> '
>
> test_expect_success 'sparse-index is not expanded: write-tree' '
> @@ -2080,7 +2090,7 @@ test_expect_success 'sparse-index is not expanded: write-tree' '
>
> echo "test1" >>sparse-index/a &&
> git -C sparse-index update-index a &&
> - ensure_not_expanded write-tree
> + ensure_not_expanded write-tree
nit: trailing whitespace should be removed
> '
>
> test_done
next prev parent reply other threads:[~2023-04-21 21:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 0:01 [RFC][PATCH v1] write-tree: integrate with sparse index Shuqi Liang
2023-04-03 20:58 ` Junio C Hamano
2023-04-03 22:16 ` Shuqi Liang
2023-04-03 22:54 ` Junio C Hamano
2023-04-04 0:35 ` [PATCH v2] " Shuqi Liang
2023-04-05 17:31 ` Victoria Dye
2023-04-05 19:48 ` Junio C Hamano
2023-04-19 7:21 ` [PATCH v3] " Shuqi Liang
2023-04-19 15:47 ` Junio C Hamano
2023-04-20 5:24 ` Shuqi Liang
2023-04-20 15:55 ` Junio C Hamano
2023-04-21 0:41 ` [PATCH v4] " Shuqi Liang
2023-04-21 21:42 ` Victoria Dye [this message]
2023-04-24 15:14 ` Junio C Hamano
2023-04-23 7:12 ` [PATCH v5] write-tree: optimize sparse integration Shuqi Liang
2023-04-24 16:00 ` Junio C Hamano
2023-05-08 20:05 ` [PATCH v6] " Shuqi Liang
2023-05-08 20:21 ` Shuqi Liang
2023-05-08 21:09 ` Junio C Hamano
2023-05-08 21:27 ` Shuqi Liang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b2a754c-6162-54d9-e9ba-fd994058066c@github.com \
--to=vdye@github$(echo .)com \
--cc=cheskaqiqi@gmail$(echo .)com \
--cc=derrickstolee@github$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox