* [PATCH v6 0/1] grep: integrate with sparse index
@ 2022-09-23 4:15 Shaoxuan Yuan
2022-09-23 4:15 ` [PATCH v6 1/1] builtin/grep.c: " Shaoxuan Yuan
2022-09-23 4:21 ` [PATCH v6 0/1] grep: " Shaoxuan Yuan
0 siblings, 2 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-09-23 4:15 UTC (permalink / raw)
To: git, newren, avarab; +Cc: derrickstolee, gitster, vdye, Shaoxuan Yuan
Integrate `git-grep` with sparse-index and test the performance
improvement.
Changes since v5
----------------
* Drop the `--sparse` option patch and edit corresponding tests.
We can wait until a better name is decided to replace `--sparse`.
* Modify the commit message, especially get rid of the `--sparse`
occurences.
Changes since v4
----------------
* Reset the length of `struct strbuf name` back to `name_base_len`,
instead of 0, after `grep_tree()` returns.
* Add test cases in t1092 for `grep` recursing into submodules.
* Add a few NEEDSWORK to explain the current problem with submodules.
Changes since v3
----------------
* Shorten the perf result tables in commit message.
* Update the commit message to reflect the changes in the commit.
* Update the commit message to indicate the performance improvement
is dependent on the pathspec.
* Stop passing `ce_mode` through `check_attr`. Instead, set the
`base_len` to 0 to make the code more reasonable and less abuse of
`check_attr`.
* Remove another invention of `base`. Use the existing `name` as the
argument for `grep_tree()`, and reset it back to `ce->name` after
`grep_tree()` returns.
* Update the p2000 test to use a more general pathspec for better
compatibility (i.e. do not use git repository specific pathspec).
* Add tests to t1092 'grep is not expanded' to verify the change
brought by "builtin/grep.c: walking tree instead of expanding index
with --sparse": the index *never* expands.
Changes since v2
----------------
* Modify the commit message for "builtin/grep.c: integrate with sparse
index" to make it obvious that the perf test results are not from
p2000 tests, but from manual perf runs.
* Add tree-walking logic as an extra (the third) patch to improve the
performance when --sparse is used. This resolved the left-over-bit
in v2 [1].
[1] https://lore.kernel.org/git/20220829232843.183711-1-shaoxuan.yuan02@gmail.com/
Changes since v1
----------------
* Rewrite the commit message for "builtin/grep.c: add --sparse option"
to be clearer.
* Update the documentation (both in-code and man page) for --sparse.
* Add a few tests to test the new behavior (when _only_ --cached is
supplied).
* Reformat the perf test results to not look like directly from p2000
tests.
* Put the "command_requires_full_index" lines right after parse_options().
* Add a pathspec test in t1092, and reword a few test documentations.
Shaoxuan Yuan (1):
builtin/grep.c: integrate with sparse index
builtin/grep.c | 48 +++++++++++++++-
t/perf/p2000-sparse-operations.sh | 1 +
t/t1092-sparse-checkout-compatibility.sh | 72 ++++++++++++++++++++++++
3 files changed, 118 insertions(+), 3 deletions(-)
Range-diff against v5:
1: 1d00d23bf9 < -: ---------- builtin/grep.c: add --sparse option
2: 926b8d2462 < -: ---------- builtin/grep.c: integrate with sparse index
3: 18b65034fe ! 1: 8604111d74 builtin/grep.c: walking tree instead of expanding index with --sparse
@@ Metadata
Author: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
## Commit message ##
- builtin/grep.c: walking tree instead of expanding index with --sparse
+ builtin/grep.c: integrate with sparse index
- Before this patch, whenever --sparse is used, `git-grep` utilizes the
- ensure_full_index() method to expand the index and search all the
- entries. Because this method requires walking all the trees and
- constructing the index, it is the slow part within the whole command.
+ Turn on sparse index and remove ensure_full_index().
+
+ Before this patch, `git-grep` utilizes the ensure_full_index() method to
+ expand the index and search all the entries. Because this method
+ requires walking all the trees and constructing the index, it is the
+ slow part within the whole command.
To achieve better performance, this patch uses grep_tree() to search the
sparse directory entries and get rid of the ensure_full_index() method.
@@ Commit message
result of expanding the index.
2) grep_tree() utilizes pathspecs to limit the scope of searching.
- ensure_full_index() always expands the index when --sparse is used,
- that means it will always walk all the trees and blobs in the repo
- without caring if the user only wants a subset of the content, i.e.
- using a pathspec. On the other hand, grep_tree() will only search
- the contents that match the pathspec, and thus possibly walking fewer
- trees.
+ ensure_full_index() always expands the index, which means it will
+ always walk all the trees and blobs in the repo without caring if
+ the user only wants a subset of the content, i.e. using a pathspec.
+ On the other hand, grep_tree() will only search the contents that
+ match the pathspec, and thus possibly walking fewer trees.
3) grep_tree() does not construct and copy back a new index, while
ensure_full_index() does. This also saves some time.
@@ Commit message
- Summary:
p2000 tests demonstrate a ~71% execution time reduction for
- `git grep --cached --sparse bogus -- "f2/f1/f1/*"` using tree-walking
- logic. However, notice that this result varies depending on the pathspec
+ `git grep --cached bogus -- "f2/f1/f1/*"` using tree-walking logic.
+ However, notice that this result varies depending on the pathspec
given. See below "Command used for testing" for more details.
Test HEAD~ HEAD
@@ Commit message
- Command used for testing:
- git grep --cached --sparse bogus -- "f2/f1/f1/*"
+ git grep --cached bogus -- "f2/f1/f1/*"
The reason for specifying a pathspec is that, if we don't specify a
pathspec, then grep_tree() will walk all the trees and blobs to find the
@@ Commit message
Command used:
- git grep --cached --sparse bogus
+ git grep --cached bogus
Test HEAD~ HEAD
---------------------------------------------------
@@ Commit message
Suggested-by: Derrick Stolee <derrickstolee@github.com>
Helped-by: Derrick Stolee <derrickstolee@github.com>
Helped-by: Victoria Dye <vdye@github.com>
+ Helped-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
## builtin/grep.c ##
@@ builtin/grep.c: static int grep_cache(struct grep_opt *opt,
if (repo_read_index(repo) < 0)
die(_("index file corrupt"));
-- if (grep_sparse)
-- ensure_full_index(repo->index);
--
+- /* TODO: audit for interaction with sparse-index. */
+- ensure_full_index(repo->index);
for (nr = 0; nr < repo->index->cache_nr; nr++) {
const struct cache_entry *ce = repo->index->cache[nr];
@@ builtin/grep.c: static int grep_cache(struct grep_opt *opt,
+ struct tree_desc tree;
+ void *data;
+ unsigned long size;
-+
-+ data = read_object_file(&ce->oid, &type, &size);
-+ init_tree_desc(&tree, data, size);
- if (S_ISREG(ce->ce_mode) &&
++ data = read_object_file(&ce->oid, &type, &size);
++ init_tree_desc(&tree, data, size);
++
+ hit |= grep_tree(opt, pathspec, &tree, &name, 0, 0);
+ strbuf_setlen(&name, name_base_len);
+ strbuf_addstr(&name, ce->name);
@@ builtin/grep.c: static int grep_cache(struct grep_opt *opt,
match_pathspec(repo->index, pathspec, name.buf, name.len, 0, NULL,
S_ISDIR(ce->ce_mode) ||
S_ISGITLINK(ce->ce_mode))) {
+@@ builtin/grep.c: int cmd_grep(int argc, const char **argv, const char *prefix)
+ PARSE_OPT_KEEP_DASHDASH |
+ PARSE_OPT_STOP_AT_NON_OPTION);
+
++ if (the_repository->gitdir) {
++ prepare_repo_settings(the_repository);
++ the_repository->settings.command_requires_full_index = 0;
++ }
++
+ if (use_index && !startup_info->have_repository) {
+ int fallback = 0;
+ git_config_get_bool("grep.fallbacktonoindex", &fallback);
## t/perf/p2000-sparse-operations.sh ##
@@ t/perf/p2000-sparse-operations.sh: test_perf_on_all git read-tree -mu HEAD
@@ t/t1092-sparse-checkout-compatibility.sh: init_repos () {
run_on_sparse () {
(
cd sparse-checkout &&
-@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'grep is not expanded' '
+@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'sparse index is not expanded: rm' '
+ ensure_not_expanded rm -r deep
+ '
- # All files within the folder1/* pathspec are sparse,
- # so this command does not find any matches
-- ensure_not_expanded ! grep a -- folder1/*
++test_expect_success 'grep with and --cached' '
++ init_repos &&
++
++ test_all_match git grep --cached a &&
++ test_all_match git grep --cached a -- "folder1/*"
++'
++
++test_expect_success 'grep is not expanded' '
++ init_repos &&
++
++ ensure_not_expanded grep a &&
++ ensure_not_expanded grep a -- deep/* &&
++
++ # All files within the folder1/* pathspec are sparse,
++ # so this command does not find any matches
+ ensure_not_expanded ! grep a -- folder1/* &&
+
+ # test out-of-cone pathspec with or without wildcard
-+ ensure_not_expanded grep --sparse --cached a -- "folder1/a" &&
-+ ensure_not_expanded grep --sparse --cached a -- "folder1/*" &&
++ ensure_not_expanded grep --cached a -- "folder1/a" &&
++ ensure_not_expanded grep --cached a -- "folder1/*" &&
+
+ # test in-cone pathspec with or without wildcard
-+ ensure_not_expanded grep --sparse --cached a -- "deep/a" &&
-+ ensure_not_expanded grep --sparse --cached a -- "deep/*"
++ ensure_not_expanded grep --cached a -- "deep/a" &&
++ ensure_not_expanded grep --cached a -- "deep/*"
+'
+
+# NEEDSWORK: when running `grep` in the superproject with --recurse-submodules,
@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'grep is not expan
+ # do not use ensure_not_expanded() here, becasue `grep` should be
+ # run in the superproject, not in "./sparse-index"
+ GIT_TRACE2_EVENT="$(pwd)/trace2.txt" \
-+ git grep --sparse --cached --recurse-submodules a -- "*/folder1/*" &&
++ git grep --cached --recurse-submodules a -- "*/folder1/*" &&
+ test_region ! index ensure_full_index trace2.txt
+'
+
@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'grep is not expan
+ sparse-checkout/folder1/a:a
+ sparse-index/folder1/a:a
+ EOF
-+ git grep --sparse --cached --recurse-submodules a -- "*/folder1/*" >actual &&
++ git grep --cached --recurse-submodules a -- "*/folder1/*" >actual &&
+ test_cmp actual expect
- '
-
++'
++
test_done
base-commit: 1b3d6e17fe83eb6f79ffbac2f2c61bbf1eaef5f8
--
2.37.0
^ permalink raw reply [flat|nested] 7+ messages in thread
* [PATCH v6 1/1] builtin/grep.c: integrate with sparse index
2022-09-23 4:15 [PATCH v6 0/1] grep: integrate with sparse index Shaoxuan Yuan
@ 2022-09-23 4:15 ` Shaoxuan Yuan
2022-09-23 4:21 ` [PATCH v6 0/1] grep: " Shaoxuan Yuan
1 sibling, 0 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-09-23 4:15 UTC (permalink / raw)
To: git, newren, avarab; +Cc: derrickstolee, gitster, vdye, Shaoxuan Yuan
Turn on sparse index and remove ensure_full_index().
Before this patch, `git-grep` utilizes the ensure_full_index() method to
expand the index and search all the entries. Because this method
requires walking all the trees and constructing the index, it is the
slow part within the whole command.
To achieve better performance, this patch uses grep_tree() to search the
sparse directory entries and get rid of the ensure_full_index() method.
Why grep_tree() is a better choice over ensure_full_index()?
1) grep_tree() is as correct as ensure_full_index(). grep_tree() looks
into every sparse-directory entry (represented by a tree) recursively
when looping over the index, and the result of doing so matches the
result of expanding the index.
2) grep_tree() utilizes pathspecs to limit the scope of searching.
ensure_full_index() always expands the index, which means it will
always walk all the trees and blobs in the repo without caring if
the user only wants a subset of the content, i.e. using a pathspec.
On the other hand, grep_tree() will only search the contents that
match the pathspec, and thus possibly walking fewer trees.
3) grep_tree() does not construct and copy back a new index, while
ensure_full_index() does. This also saves some time.
----------------
Performance test
- Summary:
p2000 tests demonstrate a ~71% execution time reduction for
`git grep --cached bogus -- "f2/f1/f1/*"` using tree-walking logic.
However, notice that this result varies depending on the pathspec
given. See below "Command used for testing" for more details.
Test HEAD~ HEAD
-------------------------------------------------------
2000.78: git grep ... (full-v3) 0.35 0.39 (≈)
2000.79: git grep ... (full-v4) 0.36 0.30 (≈)
2000.80: git grep ... (sparse-v3) 0.88 0.23 (-73.8%)
2000.81: git grep ... (sparse-v4) 0.83 0.26 (-68.6%)
- Command used for testing:
git grep --cached bogus -- "f2/f1/f1/*"
The reason for specifying a pathspec is that, if we don't specify a
pathspec, then grep_tree() will walk all the trees and blobs to find the
pattern, and the time consumed doing so is not too different from using
the original ensure_full_index() method, which also spends most of the
time walking trees. However, when a pathspec is specified, this latest
logic will only walk the area of trees enclosed by the pathspec, and the
time consumed is reasonably a lot less.
Generally speaking, because the performance gain is acheived by walking
less trees, which are specified by the pathspec, the HEAD time v.s.
HEAD~ time in sparse-v[3|4], should be proportional to
"pathspec enclosed area" v.s. "all area", respectively. Namely, the
wider the <pathspec> is encompassing, the less the performance
difference between HEAD~ and HEAD, and vice versa.
That is, if we don't specify a pathspec, the performance difference [1]
is indistinguishable: both methods walk all the trees and take generally
same amount of time (even with the index construction time included for
ensure_full_index()).
[1] Performance test result without pathspec (hence walking all trees):
Command used:
git grep --cached bogus
Test HEAD~ HEAD
---------------------------------------------------
2000.78: git grep ... (full-v3) 6.17 5.19 (≈)
2000.79: git grep ... (full-v4) 6.19 5.46 (≈)
2000.80: git grep ... (sparse-v3) 6.57 6.44 (≈)
2000.81: git grep ... (sparse-v4) 6.65 6.28 (≈)
--------------------------
NEEDSWORK about submodules
There are a few NEEDSWORKs that belong to improvements beyond this
topic. See the NEEDSWORK in builtin/grep.c::grep_submodule() for
more context. The other two NEEDSWORKs in t1092 are also relative.
Suggested-by: Derrick Stolee <derrickstolee@github.com>
Helped-by: Derrick Stolee <derrickstolee@github.com>
Helped-by: Victoria Dye <vdye@github.com>
Helped-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
---
builtin/grep.c | 48 +++++++++++++++-
t/perf/p2000-sparse-operations.sh | 1 +
t/t1092-sparse-checkout-compatibility.sh | 72 ++++++++++++++++++++++++
3 files changed, 118 insertions(+), 3 deletions(-)
diff --git a/builtin/grep.c b/builtin/grep.c
index e6bcdf860c..5fa927d4e2 100644
--- a/builtin/grep.c
+++ b/builtin/grep.c
@@ -458,6 +458,33 @@ static int grep_submodule(struct grep_opt *opt,
* subrepo's odbs to the in-memory alternates list.
*/
obj_read_lock();
+
+ /*
+ * NEEDSWORK: when reading a submodule, the sparsity settings in the
+ * superproject are incorrectly forgotten or misused. For example:
+ *
+ * 1. "command_requires_full_index"
+ * When this setting is turned on for `grep`, only the superproject
+ * knows it. All the submodules are read with their own configs
+ * and get prepare_repo_settings()'d. Therefore, these submodules
+ * "forget" the sparse-index feature switch. As a result, the index
+ * of these submodules are expanded unexpectedly.
+ *
+ * 2. "core_apply_sparse_checkout"
+ * When running `grep` in the superproject, this setting is
+ * populated using the superproject's configs. However, once
+ * initialized, this config is globally accessible and is read by
+ * prepare_repo_settings() for the submodules. For instance, if a
+ * submodule is using a sparse-checkout, however, the superproject
+ * is not, the result is that the config from the superproject will
+ * dictate the behavior for the submodule, making it "forget" its
+ * sparse-checkout state.
+ *
+ * 3. "core_sparse_checkout_cone"
+ * ditto.
+ *
+ * Note that this list is not exhaustive.
+ */
repo_read_gitmodules(subrepo, 0);
/*
@@ -520,8 +547,6 @@ static int grep_cache(struct grep_opt *opt,
if (repo_read_index(repo) < 0)
die(_("index file corrupt"));
- /* TODO: audit for interaction with sparse-index. */
- ensure_full_index(repo->index);
for (nr = 0; nr < repo->index->cache_nr; nr++) {
const struct cache_entry *ce = repo->index->cache[nr];
@@ -530,8 +555,20 @@ static int grep_cache(struct grep_opt *opt,
strbuf_setlen(&name, name_base_len);
strbuf_addstr(&name, ce->name);
+ if (S_ISSPARSEDIR(ce->ce_mode)) {
+ enum object_type type;
+ struct tree_desc tree;
+ void *data;
+ unsigned long size;
- if (S_ISREG(ce->ce_mode) &&
+ data = read_object_file(&ce->oid, &type, &size);
+ init_tree_desc(&tree, data, size);
+
+ hit |= grep_tree(opt, pathspec, &tree, &name, 0, 0);
+ strbuf_setlen(&name, name_base_len);
+ strbuf_addstr(&name, ce->name);
+ free(data);
+ } else if (S_ISREG(ce->ce_mode) &&
match_pathspec(repo->index, pathspec, name.buf, name.len, 0, NULL,
S_ISDIR(ce->ce_mode) ||
S_ISGITLINK(ce->ce_mode))) {
@@ -984,6 +1021,11 @@ int cmd_grep(int argc, const char **argv, const char *prefix)
PARSE_OPT_KEEP_DASHDASH |
PARSE_OPT_STOP_AT_NON_OPTION);
+ if (the_repository->gitdir) {
+ prepare_repo_settings(the_repository);
+ the_repository->settings.command_requires_full_index = 0;
+ }
+
if (use_index && !startup_info->have_repository) {
int fallback = 0;
git_config_get_bool("grep.fallbacktonoindex", &fallback);
diff --git a/t/perf/p2000-sparse-operations.sh b/t/perf/p2000-sparse-operations.sh
index fce8151d41..3242cfe91a 100755
--- a/t/perf/p2000-sparse-operations.sh
+++ b/t/perf/p2000-sparse-operations.sh
@@ -124,5 +124,6 @@ test_perf_on_all git read-tree -mu HEAD
test_perf_on_all git checkout-index -f --all
test_perf_on_all git update-index --add --remove $SPARSE_CONE/a
test_perf_on_all "git rm -f $SPARSE_CONE/a && git checkout HEAD -- $SPARSE_CONE/a"
+test_perf_on_all git grep --cached --sparse bogus -- "f2/f1/f1/*"
test_done
diff --git a/t/t1092-sparse-checkout-compatibility.sh b/t/t1092-sparse-checkout-compatibility.sh
index b9350c075c..711b52fb46 100755
--- a/t/t1092-sparse-checkout-compatibility.sh
+++ b/t/t1092-sparse-checkout-compatibility.sh
@@ -162,6 +162,19 @@ init_repos () {
git -C sparse-index sparse-checkout set deep
}
+init_repos_as_submodules () {
+ git reset --hard &&
+ init_repos &&
+ git submodule add ./full-checkout &&
+ git submodule add ./sparse-checkout &&
+ git submodule add ./sparse-index &&
+
+ git submodule status >actual &&
+ grep full-checkout actual &&
+ grep sparse-checkout actual &&
+ grep sparse-index actual
+}
+
run_on_sparse () {
(
cd sparse-checkout &&
@@ -1981,4 +1994,63 @@ test_expect_success 'sparse index is not expanded: rm' '
ensure_not_expanded rm -r deep
'
+test_expect_success 'grep with and --cached' '
+ init_repos &&
+
+ test_all_match git grep --cached a &&
+ test_all_match git grep --cached a -- "folder1/*"
+'
+
+test_expect_success 'grep is not expanded' '
+ init_repos &&
+
+ ensure_not_expanded grep a &&
+ ensure_not_expanded grep a -- deep/* &&
+
+ # All files within the folder1/* pathspec are sparse,
+ # so this command does not find any matches
+ ensure_not_expanded ! grep a -- folder1/* &&
+
+ # test out-of-cone pathspec with or without wildcard
+ ensure_not_expanded grep --cached a -- "folder1/a" &&
+ ensure_not_expanded grep --cached a -- "folder1/*" &&
+
+ # test in-cone pathspec with or without wildcard
+ ensure_not_expanded grep --cached a -- "deep/a" &&
+ ensure_not_expanded grep --cached a -- "deep/*"
+'
+
+# NEEDSWORK: when running `grep` in the superproject with --recurse-submodules,
+# Git expands the index of the submodules unexpectedly. Even though `grep`
+# builtin is marked as "command_requires_full_index = 0", this config is only
+# useful for the superproject. Namely, the submodules have their own configs,
+# which are _not_ populated by the one-time sparse-index feature switch.
+test_expect_failure 'grep within submodules is not expanded' '
+ init_repos_as_submodules &&
+
+ # do not use ensure_not_expanded() here, becasue `grep` should be
+ # run in the superproject, not in "./sparse-index"
+ GIT_TRACE2_EVENT="$(pwd)/trace2.txt" \
+ git grep --cached --recurse-submodules a -- "*/folder1/*" &&
+ test_region ! index ensure_full_index trace2.txt
+'
+
+# NEEDSWORK: this test is not actually testing the code. The design purpose
+# of this test is to verify the grep result when the submodules are using a
+# sparse-index. Namely, we want "folder1/" as a tree (a sparse directory); but
+# because of the index expansion, we are now grepping the "folder1/a" blob.
+# Because of the problem stated above 'grep within submodules is not expanded',
+# we don't have the ideal test environment yet.
+test_expect_success 'grep sparse directory within submodules' '
+ init_repos_as_submodules &&
+
+ cat >expect <<-\EOF &&
+ full-checkout/folder1/a:a
+ sparse-checkout/folder1/a:a
+ sparse-index/folder1/a:a
+ EOF
+ git grep --cached --recurse-submodules a -- "*/folder1/*" >actual &&
+ test_cmp actual expect
+'
+
test_done
--
2.37.0
^ permalink raw reply related [flat|nested] 7+ messages in thread
* [PATCH v6 0/1] grep: integrate with sparse index
2022-08-17 7:56 [PATCH v1 0/2] " Shaoxuan Yuan
@ 2022-09-23 4:18 ` Shaoxuan Yuan
2022-09-23 14:13 ` Derrick Stolee
2022-09-23 16:01 ` Victoria Dye
0 siblings, 2 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-09-23 4:18 UTC (permalink / raw)
To: git; +Cc: derrickstolee, gitster, vdye, newren, avarab, Shaoxuan Yuan
Integrate `git-grep` with sparse-index and test the performance
improvement.
Changes since v5
----------------
* Drop the `--sparse` option patch and edit corresponding tests.
We can wait until a better name is decided to replace `--sparse`.
* Modify the commit message, especially get rid of the `--sparse`
occurences.
Changes since v4
----------------
* Reset the length of `struct strbuf name` back to `name_base_len`,
instead of 0, after `grep_tree()` returns.
* Add test cases in t1092 for `grep` recursing into submodules.
* Add a few NEEDSWORK to explain the current problem with submodules.
Changes since v3
----------------
* Shorten the perf result tables in commit message.
* Update the commit message to reflect the changes in the commit.
* Update the commit message to indicate the performance improvement
is dependent on the pathspec.
* Stop passing `ce_mode` through `check_attr`. Instead, set the
`base_len` to 0 to make the code more reasonable and less abuse of
`check_attr`.
* Remove another invention of `base`. Use the existing `name` as the
argument for `grep_tree()`, and reset it back to `ce->name` after
`grep_tree()` returns.
* Update the p2000 test to use a more general pathspec for better
compatibility (i.e. do not use git repository specific pathspec).
* Add tests to t1092 'grep is not expanded' to verify the change
brought by "builtin/grep.c: walking tree instead of expanding index
with --sparse": the index *never* expands.
Changes since v2
----------------
* Modify the commit message for "builtin/grep.c: integrate with sparse
index" to make it obvious that the perf test results are not from
p2000 tests, but from manual perf runs.
* Add tree-walking logic as an extra (the third) patch to improve the
performance when --sparse is used. This resolved the left-over-bit
in v2 [1].
[1] https://lore.kernel.org/git/20220829232843.183711-1-shaoxuan.yuan02@gmail.com/
Changes since v1
----------------
* Rewrite the commit message for "builtin/grep.c: add --sparse option"
to be clearer.
* Update the documentation (both in-code and man page) for --sparse.
* Add a few tests to test the new behavior (when _only_ --cached is
supplied).
* Reformat the perf test results to not look like directly from p2000
tests.
* Put the "command_requires_full_index" lines right after parse_options().
* Add a pathspec test in t1092, and reword a few test documentations.
Shaoxuan Yuan (1):
builtin/grep.c: integrate with sparse index
builtin/grep.c | 48 +++++++++++++++-
t/perf/p2000-sparse-operations.sh | 1 +
t/t1092-sparse-checkout-compatibility.sh | 72 ++++++++++++++++++++++++
3 files changed, 118 insertions(+), 3 deletions(-)
Range-diff against v5:
1: 1d00d23bf9 < -: ---------- builtin/grep.c: add --sparse option
2: 926b8d2462 < -: ---------- builtin/grep.c: integrate with sparse index
3: 18b65034fe ! 1: 8604111d74 builtin/grep.c: walking tree instead of expanding index with --sparse
@@ Metadata
Author: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
## Commit message ##
- builtin/grep.c: walking tree instead of expanding index with --sparse
+ builtin/grep.c: integrate with sparse index
- Before this patch, whenever --sparse is used, `git-grep` utilizes the
- ensure_full_index() method to expand the index and search all the
- entries. Because this method requires walking all the trees and
- constructing the index, it is the slow part within the whole command.
+ Turn on sparse index and remove ensure_full_index().
+
+ Before this patch, `git-grep` utilizes the ensure_full_index() method to
+ expand the index and search all the entries. Because this method
+ requires walking all the trees and constructing the index, it is the
+ slow part within the whole command.
To achieve better performance, this patch uses grep_tree() to search the
sparse directory entries and get rid of the ensure_full_index() method.
@@ Commit message
result of expanding the index.
2) grep_tree() utilizes pathspecs to limit the scope of searching.
- ensure_full_index() always expands the index when --sparse is used,
- that means it will always walk all the trees and blobs in the repo
- without caring if the user only wants a subset of the content, i.e.
- using a pathspec. On the other hand, grep_tree() will only search
- the contents that match the pathspec, and thus possibly walking fewer
- trees.
+ ensure_full_index() always expands the index, which means it will
+ always walk all the trees and blobs in the repo without caring if
+ the user only wants a subset of the content, i.e. using a pathspec.
+ On the other hand, grep_tree() will only search the contents that
+ match the pathspec, and thus possibly walking fewer trees.
3) grep_tree() does not construct and copy back a new index, while
ensure_full_index() does. This also saves some time.
@@ Commit message
- Summary:
p2000 tests demonstrate a ~71% execution time reduction for
- `git grep --cached --sparse bogus -- "f2/f1/f1/*"` using tree-walking
- logic. However, notice that this result varies depending on the pathspec
+ `git grep --cached bogus -- "f2/f1/f1/*"` using tree-walking logic.
+ However, notice that this result varies depending on the pathspec
given. See below "Command used for testing" for more details.
Test HEAD~ HEAD
@@ Commit message
- Command used for testing:
- git grep --cached --sparse bogus -- "f2/f1/f1/*"
+ git grep --cached bogus -- "f2/f1/f1/*"
The reason for specifying a pathspec is that, if we don't specify a
pathspec, then grep_tree() will walk all the trees and blobs to find the
@@ Commit message
Command used:
- git grep --cached --sparse bogus
+ git grep --cached bogus
Test HEAD~ HEAD
---------------------------------------------------
@@ Commit message
Suggested-by: Derrick Stolee <derrickstolee@github.com>
Helped-by: Derrick Stolee <derrickstolee@github.com>
Helped-by: Victoria Dye <vdye@github.com>
+ Helped-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
## builtin/grep.c ##
@@ builtin/grep.c: static int grep_cache(struct grep_opt *opt,
if (repo_read_index(repo) < 0)
die(_("index file corrupt"));
-- if (grep_sparse)
-- ensure_full_index(repo->index);
--
+- /* TODO: audit for interaction with sparse-index. */
+- ensure_full_index(repo->index);
for (nr = 0; nr < repo->index->cache_nr; nr++) {
const struct cache_entry *ce = repo->index->cache[nr];
@@ builtin/grep.c: static int grep_cache(struct grep_opt *opt,
+ struct tree_desc tree;
+ void *data;
+ unsigned long size;
-+
-+ data = read_object_file(&ce->oid, &type, &size);
-+ init_tree_desc(&tree, data, size);
- if (S_ISREG(ce->ce_mode) &&
++ data = read_object_file(&ce->oid, &type, &size);
++ init_tree_desc(&tree, data, size);
++
+ hit |= grep_tree(opt, pathspec, &tree, &name, 0, 0);
+ strbuf_setlen(&name, name_base_len);
+ strbuf_addstr(&name, ce->name);
@@ builtin/grep.c: static int grep_cache(struct grep_opt *opt,
match_pathspec(repo->index, pathspec, name.buf, name.len, 0, NULL,
S_ISDIR(ce->ce_mode) ||
S_ISGITLINK(ce->ce_mode))) {
+@@ builtin/grep.c: int cmd_grep(int argc, const char **argv, const char *prefix)
+ PARSE_OPT_KEEP_DASHDASH |
+ PARSE_OPT_STOP_AT_NON_OPTION);
+
++ if (the_repository->gitdir) {
++ prepare_repo_settings(the_repository);
++ the_repository->settings.command_requires_full_index = 0;
++ }
++
+ if (use_index && !startup_info->have_repository) {
+ int fallback = 0;
+ git_config_get_bool("grep.fallbacktonoindex", &fallback);
## t/perf/p2000-sparse-operations.sh ##
@@ t/perf/p2000-sparse-operations.sh: test_perf_on_all git read-tree -mu HEAD
@@ t/t1092-sparse-checkout-compatibility.sh: init_repos () {
run_on_sparse () {
(
cd sparse-checkout &&
-@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'grep is not expanded' '
+@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'sparse index is not expanded: rm' '
+ ensure_not_expanded rm -r deep
+ '
- # All files within the folder1/* pathspec are sparse,
- # so this command does not find any matches
-- ensure_not_expanded ! grep a -- folder1/*
++test_expect_success 'grep with and --cached' '
++ init_repos &&
++
++ test_all_match git grep --cached a &&
++ test_all_match git grep --cached a -- "folder1/*"
++'
++
++test_expect_success 'grep is not expanded' '
++ init_repos &&
++
++ ensure_not_expanded grep a &&
++ ensure_not_expanded grep a -- deep/* &&
++
++ # All files within the folder1/* pathspec are sparse,
++ # so this command does not find any matches
+ ensure_not_expanded ! grep a -- folder1/* &&
+
+ # test out-of-cone pathspec with or without wildcard
-+ ensure_not_expanded grep --sparse --cached a -- "folder1/a" &&
-+ ensure_not_expanded grep --sparse --cached a -- "folder1/*" &&
++ ensure_not_expanded grep --cached a -- "folder1/a" &&
++ ensure_not_expanded grep --cached a -- "folder1/*" &&
+
+ # test in-cone pathspec with or without wildcard
-+ ensure_not_expanded grep --sparse --cached a -- "deep/a" &&
-+ ensure_not_expanded grep --sparse --cached a -- "deep/*"
++ ensure_not_expanded grep --cached a -- "deep/a" &&
++ ensure_not_expanded grep --cached a -- "deep/*"
+'
+
+# NEEDSWORK: when running `grep` in the superproject with --recurse-submodules,
@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'grep is not expan
+ # do not use ensure_not_expanded() here, becasue `grep` should be
+ # run in the superproject, not in "./sparse-index"
+ GIT_TRACE2_EVENT="$(pwd)/trace2.txt" \
-+ git grep --sparse --cached --recurse-submodules a -- "*/folder1/*" &&
++ git grep --cached --recurse-submodules a -- "*/folder1/*" &&
+ test_region ! index ensure_full_index trace2.txt
+'
+
@@ t/t1092-sparse-checkout-compatibility.sh: test_expect_success 'grep is not expan
+ sparse-checkout/folder1/a:a
+ sparse-index/folder1/a:a
+ EOF
-+ git grep --sparse --cached --recurse-submodules a -- "*/folder1/*" >actual &&
++ git grep --cached --recurse-submodules a -- "*/folder1/*" >actual &&
+ test_cmp actual expect
- '
-
++'
++
test_done
base-commit: 1b3d6e17fe83eb6f79ffbac2f2c61bbf1eaef5f8
--
2.37.0
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v6 0/1] grep: integrate with sparse index
2022-09-23 4:15 [PATCH v6 0/1] grep: integrate with sparse index Shaoxuan Yuan
2022-09-23 4:15 ` [PATCH v6 1/1] builtin/grep.c: " Shaoxuan Yuan
@ 2022-09-23 4:21 ` Shaoxuan Yuan
1 sibling, 0 replies; 7+ messages in thread
From: Shaoxuan Yuan @ 2022-09-23 4:21 UTC (permalink / raw)
To: git, newren, avarab; +Cc: derrickstolee, gitster, vdye
Oh, shoot...
Sorry that I forgot to "--in-reply-to", please ignore this thread :(
Thanks,
Shaoxuan
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v6 0/1] grep: integrate with sparse index
2022-09-23 4:18 ` [PATCH v6 0/1] " Shaoxuan Yuan
@ 2022-09-23 14:13 ` Derrick Stolee
2022-09-23 16:01 ` Victoria Dye
1 sibling, 0 replies; 7+ messages in thread
From: Derrick Stolee @ 2022-09-23 14:13 UTC (permalink / raw)
To: Shaoxuan Yuan, git; +Cc: gitster, vdye, newren, avarab
On 9/23/2022 12:18 AM, Shaoxuan Yuan wrote:
> Integrate `git-grep` with sparse-index and test the performance
> improvement.
>
> Changes since v5
> ----------------
>
> * Drop the `--sparse` option patch and edit corresponding tests.
> We can wait until a better name is decided to replace `--sparse`.
>
> * Modify the commit message, especially get rid of the `--sparse`
> occurences.
It's nice that now that you are calling grep_tree() when reaching a
sparse directory entry, you can still have all of the ensure_not_expanded
tests work even without --sparse.
There is definitely room for improving the user experience to focus on
the sparse cone by implementing a replacement for --sparse in the future,
especially for users with partial clones.
But this patch stands on its own. Thank you for your hard work here.
Thanks,
-Stolee
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v6 0/1] grep: integrate with sparse index
2022-09-23 4:18 ` [PATCH v6 0/1] " Shaoxuan Yuan
2022-09-23 14:13 ` Derrick Stolee
@ 2022-09-23 16:01 ` Victoria Dye
2022-09-23 17:08 ` Junio C Hamano
1 sibling, 1 reply; 7+ messages in thread
From: Victoria Dye @ 2022-09-23 16:01 UTC (permalink / raw)
To: Shaoxuan Yuan, git; +Cc: derrickstolee, gitster, newren, avarab
Shaoxuan Yuan wrote:
> Integrate `git-grep` with sparse-index and test the performance
> improvement.
>
> Changes since v5
> ----------------
>
> * Drop the `--sparse` option patch and edit corresponding tests.
> We can wait until a better name is decided to replace `--sparse`.
>
> * Modify the commit message, especially get rid of the `--sparse`
> occurences.
>
Thanks for the update! Everything in this patch is either part of the
previous version's patch 3 or comes from the tests & sparse index enabling
of the previous patch 2. The resulting patch enables the sparse index for
all usage of '--cached', and avoids any user option changes.
All that to say, this version looks good to me!
Thanks!
- Victoria
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH v6 0/1] grep: integrate with sparse index
2022-09-23 16:01 ` Victoria Dye
@ 2022-09-23 17:08 ` Junio C Hamano
0 siblings, 0 replies; 7+ messages in thread
From: Junio C Hamano @ 2022-09-23 17:08 UTC (permalink / raw)
To: Victoria Dye; +Cc: Shaoxuan Yuan, git, derrickstolee, newren, avarab
Victoria Dye <vdye@github.com> writes:
> Shaoxuan Yuan wrote:
>> Integrate `git-grep` with sparse-index and test the performance
>> improvement.
>>
>> Changes since v5
>> ----------------
>>
>> * Drop the `--sparse` option patch and edit corresponding tests.
>> We can wait until a better name is decided to replace `--sparse`.
>>
>> * Modify the commit message, especially get rid of the `--sparse`
>> occurences.
>>
>
> Thanks for the update! Everything in this patch is either part of the
> previous version's patch 3 or comes from the tests & sparse index enabling
> of the previous patch 2. The resulting patch enables the sparse index for
> all usage of '--cached', and avoids any user option changes.
>
> All that to say, this version looks good to me!
Thanks, all. Captured but outside the upcoming release so expect
that it will be slow to merge into any of the integration branches.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-09-23 17:09 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-23 4:15 [PATCH v6 0/1] grep: integrate with sparse index Shaoxuan Yuan
2022-09-23 4:15 ` [PATCH v6 1/1] builtin/grep.c: " Shaoxuan Yuan
2022-09-23 4:21 ` [PATCH v6 0/1] grep: " Shaoxuan Yuan
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 7:56 [PATCH v1 0/2] " Shaoxuan Yuan
2022-09-23 4:18 ` [PATCH v6 0/1] " Shaoxuan Yuan
2022-09-23 14:13 ` Derrick Stolee
2022-09-23 16:01 ` Victoria Dye
2022-09-23 17:08 ` Junio C Hamano
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).