From: Thomas Gummerer <t.gummerer@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: Matthias Asshauer <mha1993@live.de>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] stash: use "stash--helper"
Date: Fri, 29 Jan 2016 12:21:52 +0100 [thread overview]
Message-ID: <20160129112152.GO7100@hank> (raw)
In-Reply-To: <CAGZ79kaPQP+-LpW8ExM2wmfftW4_oa7tB5XdfsdC8XHwH4aFOA@mail.gmail.com>
On 01/28, Stefan Beller wrote:
> On Thu, Jan 28, 2016 at 12:36 PM, Matthias Asshauer <mha1993@live.de> wrote:
> > From: Matthias Aßhauer <mha1993@live.de>
> >
> > Use the new "git stash--helper" builtin. It should be faster than the old shell code and is a first step to move
> > more shell code to C.
>
> You had some good measurements in the coverletter, which is not going to be
> recorded in the projects history. This part however would be part of the commit.
> So you could move the speed improvements here (as well as the other reasoning)
> on why this is a good idea. :)
In addition it would be nice to add a performance test in t/perf,
especially since it seems further improvements are planned. That will
make it easy for everyone to reproduce the performance numbers for
different use-cases.
Matthias, feel free to squash the following (or something similar) in
when you re-roll.
diff --git a/t/perf/p3000-stash.sh b/t/perf/p3000-stash.sh
new file mode 100755
index 0000000..e6e1153
--- /dev/null
+++ b/t/perf/p3000-stash.sh
@@ -0,0 +1,20 @@
+#!/bin/sh
+
+test_description="Test performance of git stash"
+
+. ./perf-lib.sh
+
+test_perf_default_repo
+
+file=$(git ls-files | tail -n 30 | head -1)
+
+test_expect_success "prepare repository" "
+ echo x >$file
+"
+
+test_perf "stash/stash pop" "
+ git stash &&
+ git stash pop
+"
+
+test_done
next prev parent reply other threads:[~2016-01-29 11:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:38 [PATCH 0/2] Make stash a builtin Matthias Aßhauer
2016-01-28 20:36 ` [PATCH 1/2] stash--helper: implement "git stash--helper" Matthias Asshauer
2016-01-28 20:36 ` [PATCH 2/2] stash: use "stash--helper" Matthias Asshauer
2016-01-28 20:59 ` Stefan Beller
2016-01-28 21:25 ` AW: " Matthias Aßhauer
2016-01-28 21:41 ` Stefan Beller
2016-01-28 23:28 ` Roberto Tyley
2016-01-29 19:37 ` AW: " Matthias Aßhauer
2016-01-29 11:21 ` Thomas Gummerer [this message]
2016-01-29 18:34 ` Junio C Hamano
2016-01-28 23:06 ` [PATCH 1/2] stash--helper: implement "git stash--helper" Junio C Hamano
2016-01-29 19:32 ` AW: " Matthias Aßhauer
2016-01-29 19:58 ` Junio C Hamano
2016-02-01 23:36 ` Michael Blume
2016-02-01 23:40 ` Junio C Hamano
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=20160129112152.GO7100@hank \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=mha1993@live.de \
--cc=sbeller@google.com \
/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).