diff options
author | Ben Peart <benpeart@microsoft.com> | 2017-09-22 12:35:48 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2017-10-01 17:23:05 +0900 |
commit | 14527b30022190c6e7e8cd7f7dbef4195ebeedc2 (patch) | |
tree | ccc0578b8d6139da7caa33bfe10a72cf763e07f6 /Documentation/fix-texi.perl | |
parent | fsmonitor: add a sample integration script for Watchman (diff) | |
download | tgif-14527b30022190c6e7e8cd7f7dbef4195ebeedc2.tar.xz |
fsmonitor: add a performance test
Add a test utility (test-drop-caches) that flushes all changes to disk
then drops file system cache on Windows, Linux, and OSX.
Add a perf test (p7519-fsmonitor.sh) for fsmonitor.
By default, the performance test will utilize the Watchman file system
monitor if it is installed. If Watchman is not installed, it will use a
dummy integration script that does not report any new or modified files.
The dummy script has very little overhead which provides optimistic results.
The performance test will also use the untracked cache feature if it is
available as fsmonitor uses it to speed up scanning for untracked files.
There are 4 environment variables that can be used to alter the default
behavior of the performance test:
GIT_PERF_7519_UNTRACKED_CACHE: used to configure core.untrackedCache
GIT_PERF_7519_SPLIT_INDEX: used to configure core.splitIndex
GIT_PERF_7519_FSMONITOR: used to configure core.fsmonitor
GIT_PERF_7519_DROP_CACHE: if set, the OS caches are dropped between tests
The big win for using fsmonitor is the elimination of the need to scan the
working directory looking for changed and untracked files. If the file
information is all cached in RAM, the benefits are reduced.
Signed-off-by: Ben Peart <benpeart@microsoft.com>
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/fix-texi.perl')
0 files changed, 0 insertions, 0 deletions