From: Neeraj Singh <neerajsi@xxxxxxxxxxxxx>
Add a basic performance test for "git add" and "git stash" of a lot of
new objects with various fsync settings.
Signed-off-by: Neeraj Singh <neerajsi@xxxxxxxxxxxxx>
---
t/perf/p3700-add.sh | 43 ++++++++++++++++++++++++++++++++++++++++
t/perf/p3900-stash.sh | 46 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 89 insertions(+)
create mode 100755 t/perf/p3700-add.sh
create mode 100755 t/perf/p3900-stash.sh
diff --git a/t/perf/p3700-add.sh b/t/perf/p3700-add.sh
new file mode 100755
index 00000000000..e93c08a2e70
--- /dev/null
+++ b/t/perf/p3700-add.sh
@@ -0,0 +1,43 @@
+#!/bin/sh
+#
+# This test measures the performance of adding new files to the object database
+# and index. The test was originally added to measure the effect of the
+# core.fsyncObjectFiles=batch mode, which is why we are testing different values
+# of that setting explicitly and creating a lot of unique objects.
+
+test_description="Tests performance of add"
+
+. ./perf-lib.sh
+
+. $TEST_DIRECTORY/lib-unique-files.sh
+
+test_perf_default_repo
+test_checkout_worktree
+
+dir_count=10
+files_per_dir=50
+total_files=$((dir_count * files_per_dir))
+
+# We need to create the files each time we run the perf test, but
+# we do not want to measure the cost of creating the files, so run
+# the tet once.
+if test "${GIT_PERF_REPEAT_COUNT-1}" -ne 1
+then
+ echo "warning: Setting GIT_PERF_REPEAT_COUNT=1" >&2
+ GIT_PERF_REPEAT_COUNT=1
+fi
+
+for m in false true batch
+do
+ test_expect_success "create the files for core.fsyncObjectFiles=$m" '
+ git reset --hard &&
+ # create files across directories
+ test_create_unique_files $dir_count $files_per_dir files
+ '
+
+ test_perf "add $total_files files (core.fsyncObjectFiles=$m)" "
+ git -c core.fsyncobjectfiles=$m add files
+ "
+done
+
+test_done
diff --git a/t/perf/p3900-stash.sh b/t/perf/p3900-stash.sh
new file mode 100755
index 00000000000..c9fcd0c03eb
--- /dev/null
+++ b/t/perf/p3900-stash.sh
@@ -0,0 +1,46 @@
+#!/bin/sh
+#
+# This test measures the performance of adding new files to the object database
+# and index. The test was originally added to measure the effect of the
+# core.fsyncObjectFiles=batch mode, which is why we are testing different values
+# of that setting explicitly and creating a lot of unique objects.
+
+test_description="Tests performance of stash"
+
+. ./perf-lib.sh
+
+. $TEST_DIRECTORY/lib-unique-files.sh
+
+test_perf_default_repo
+test_checkout_worktree
+
+dir_count=10
+files_per_dir=50
+total_files=$((dir_count * files_per_dir))
+
+# We need to create the files each time we run the perf test, but
+# we do not want to measure the cost of creating the files, so run
+# the tet once.
+if test "${GIT_PERF_REPEAT_COUNT-1}" -ne 1
+then
+ echo "warning: Setting GIT_PERF_REPEAT_COUNT=1" >&2
+ GIT_PERF_REPEAT_COUNT=1
+fi
+
+for m in false true batch
+do
+ test_expect_success "create the files for core.fsyncObjectFiles=$m" '
+ git reset --hard &&
+ # create files across directories
+ test_create_unique_files $dir_count $files_per_dir files
+ '
+
+ # We only stash files in the 'files' subdirectory since
+ # the perf test infrastructure creates files in the
+ # current working directory that need to be preserved
+ test_perf "stash 500 files (core.fsyncObjectFiles=$m)" "
+ git -c core.fsyncobjectfiles=$m stash push -u -- files
+ "
+done
+
+test_done
--
gitgitgadget
