From: "Erik Elfström" <erik.elfstrom@gmail.com>
To: git@vger.kernel.org
Cc: "Erik Elfström" <erik.elfstrom@gmail.com>
Subject: [PATCH/RFC v3 0/4] Improving performance of git clean
Date: Sat, 18 Apr 2015 22:41:08 +0200 [thread overview]
Message-ID: <1429389672-30209-1-git-send-email-erik.elfstrom@gmail.com> (raw)
I've marked this RFC since there are known problems here.
v2 of the patch can be found here:
http://thread.gmane.org/gmane.comp.version-control.git/267023/focus=267023
Changes in v3:
* Created setup.c:read_gitfile_gently to use for submodule
probing
* Cleanup of some tests by use of test_commit helper
* Added more tests of cleaning in the presence of submodules
* Reversed expectation of test for cleaning nested bare repos.
They are now expected to be cleaned. Added one more case.
* Fixed bug where submodules could be cleaned by using new
read_gitfile_gently for additional submodule check in
clean.c:is_git_repository
* Attempt to change behavior of patch implementation to clean
bare repositories (only partially successful)
* Reworded commit message of the performance fix commit
Known Problems:
* Unsure about the setup.c:read_gitfile refactor, feels a bit
messy?
* Potentially a missing sanity check of git file size in
setup.c:read_gitfile_gently_or_non_gently
* We still get a behavioral change for empty bare repositories
placed in a ".git" directory. Currently we clean empty bare
repos in a .git folder but not non-empty one. After this
patch we won't clean either. How serious is this? Is there
an easy fix (preferebly to clean all bare repositories)?
* Still have issues in the performance tests, see comments
from Thomas Gummerer on v2
Thanks to Junio C Hamano and Jeff King for spotting fundamental
problems in v2 and suggesting a solution.
Erik Elfström (4):
setup: add gentle version of read_gitfile
t7300: add tests to document behavior of clean and nested git
p7300: add performance tests for clean
clean: improve performance when removing lots of directories
builtin/clean.c | 25 ++++++++--
cache.h | 1 +
setup.c | 94 ++++++++++++++++++++++++++++---------
t/perf/p7300-clean.sh | 37 +++++++++++++++
t/t7300-clean.sh | 125 ++++++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 257 insertions(+), 25 deletions(-)
create mode 100755 t/perf/p7300-clean.sh
--
2.4.0.rc2.5.g2871d5e
next reply other threads:[~2015-04-18 20:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 20:41 Erik Elfström [this message]
2015-04-18 20:41 ` [PATCH/RFC v3 1/4] setup: add gentle version of read_gitfile Erik Elfström
2015-04-18 20:41 ` [PATCH/RFC v3 2/4] t7300: add tests to document behavior of clean and nested git Erik Elfström
2015-04-18 20:41 ` [PATCH/RFC v3 3/4] p7300: add performance tests for clean Erik Elfström
2015-04-18 20:41 ` [PATCH/RFC v3 4/4] clean: improve performance when removing lots of directories Erik Elfström
2015-04-19 1:14 ` [PATCH/RFC v3 0/4] Improving performance of git clean Junio C Hamano
2015-04-21 18:17 ` erik elfström
2015-04-20 22:14 ` Thomas Gummerer
2015-04-21 18:21 ` erik elfström
2015-04-21 19:02 ` Junio C Hamano
2015-04-21 21:24 ` Jeff King
2015-04-22 19:30 ` erik elfström
2015-04-22 19:46 ` Jeff King
2015-04-22 19:53 ` erik elfström
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=1429389672-30209-1-git-send-email-erik.elfstrom@gmail.com \
--to=erik.elfstrom@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).