From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <j6t@kdbg.org>, Beat Bolli <dev+git@drbeat.li>,
git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] t3900: add some more quotes
Date: Thu, 11 Jan 2018 04:38:20 -0500 [thread overview]
Message-ID: <20180111093819.GB9190@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqy3l5z9hx.fsf@gitster.mtv.corp.google.com>
On Wed, Jan 10, 2018 at 01:31:22PM -0800, Junio C Hamano wrote:
> > +# Read from stdin into the variable given in $1.
> > +test_read_to_eof () {
> > + # Bash's "read" is sufficiently flexible that we can skip the extra
> > + # process.
> > + if test -n "$BASH_VERSION"
> > + then
> > + # 64k should be enough for anyone...
> > + read -N 65536 -r "$1"
> > + else
> > + # command substitution eats trailing whitespace, so we add
> > + # and then remove a non-whitespace character.
> > + eval "$1=\$(cat; printf x)"
> > + eval "$1=\${$1%x}"
> > + fi
> > +}
>
> Yuck. Hacky but nice.
>
> I think this will make it easier to read but I suspect here text
> would use temporary files and may slow things down a bit? I do not
> know if it is even measurable, though.
Yeah, since I was able to contain the horrible-ness in this function, I
think the overall readability/portability is probably OK. My main
concern was that it would be slower (hence the bash hackery). I applied
the patch below on top to see what kind of impact we could measure
across the whole suite:
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index be8a47d304..6f2e6e7560 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -441,6 +441,15 @@ test_expect_success () {
then
test_read_to_eof test_block
set -- "$1" "$test_block"
+ else
+ # this is obviously a dumb thing to do, but it's just
+ # a performance-testing hack.
+ test_read_to_eof test_block <<EOF
+$2
+EOF
+ # our here-doc hackery added an extra newline
+ set -- "$1" "${test_block%
+}"
fi
test_verify_prereq
export test_prereq
After doing five trial timings each of "make test" on:
- stock git with dash
- this patch with dash (so using "cat" to read the here-doc)
- stock git with bash
- this patch with bash (so using an internal "read")
I couldn't come up with any definitive slowdown.
In the first two, there's a fair bit of run-to-run noise (easily 10%),
and my best run was actually _with_ the patch (by only 3%, but still the
opposite of what you'd expect).
Running the (stock) suite with bash is definitively slower than with
dash (by about 20%). Adding in this patch didn't seem to make it any
slower.
So I dunno. Maybe it's not so crazy an idea.
-Peff
next prev parent reply other threads:[~2018-01-11 9:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 9:58 [PATCH] t3900: add some more quotes Beat Bolli
2018-01-10 10:33 ` Jeff King
2018-01-10 17:21 ` Johannes Schindelin
2018-01-10 17:44 ` Eric Sunshine
2018-01-10 22:38 ` [PATCH v2] " Beat Bolli
2018-01-10 23:09 ` Johannes Schindelin
2018-01-10 23:09 ` Junio C Hamano
2018-01-10 19:02 ` [PATCH] " Johannes Sixt
2018-01-10 19:43 ` Junio C Hamano
2018-01-10 19:53 ` Jeff King
2018-01-10 21:31 ` Junio C Hamano
2018-01-11 9:38 ` Jeff King [this message]
2018-01-11 11:39 ` read test snippet from stdin [was: [PATCH] t3900: add some more quotes] SZEDER Gábor
2018-01-11 12:11 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180111093819.GB9190@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=johannes.schindelin@gmx.de \
/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.
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).