From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Stefan Beller <sbeller@google.com>, Jeff King <peff@peff.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Duy Nguyen <pclouds@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: "Cannot fetch git.git" (worktrees at fault? or origin/HEAD) ?
Date: Fri, 3 Nov 2017 15:02:52 +0530 [thread overview]
Message-ID: <0f1f8317-9d82-5e61-5332-f877ca886056@gmail.com> (raw)
In-Reply-To: <CAGZ79kYAn0Hi0qaG8P5zvVOFTsfXYrtvrR7oiT0KwwWeKLqZgw@mail.gmail.com>
On Monday 23 October 2017 11:07 PM, Stefan Beller wrote:
> Exactly. By memory I mean volatile RAM (as opposed to
> memory on a spinning disk).
>
> Using GIT_TEST_OPTS has had some issues (I remember vaguely
> there was an inconsistency between the output of `make test` and prove),
> so I put my entire working tree on a tmpfs, I run roughly this script
> after booting my computer:
>
> sudo mount -t tmpfs -o size=16g tmpfs /u
> mkdir /u/git
> echo "gitdir:
> /usr/local/google/home/sbeller/OSS/git/.git/worktrees/git"
>> /u/git/.git
> git -C /u/git checkout -f HEAD
>
> cat <<EOF >/u/config.mak
> DEVELOPER=1
> DEVELOPERS=1
> CFLAGS += -g -O2
> CFLAGS += -DFLEX_ARRAY=2048
> #CFLAGS += -Wno-unused-value
> EOF
Did I thank you for a good explanation? If not, thanks that was
interesting and enlightening.
> The test suite (excluding t9*) runs in less than 50 seconds on the ram
> disk.
>
BTW, this is what I call _way way_ faster. Unfortunately due to the
limited configuration of my system, the test suite has following timing
real 3m14.482s
user 2m10.556s
sys 1m12.328s
Anyways it's better than the timing I get for running it on a spinning
disk which takes
real 4m37.585s
user 2m17.244s
sys 1m37.136s
Thanks,
Kaartic
next prev parent reply other threads:[~2017-11-03 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 1:43 "Cannot fetch git.git" (worktrees at fault? or origin/HEAD) ? Stefan Beller
2017-10-20 3:16 ` Jeff King
2017-10-20 5:27 ` Stefan Beller
2017-10-20 6:04 ` Jeff King
2017-10-20 20:45 ` Stefan Beller
2017-10-22 14:24 ` Kaartic Sivaraam
2017-10-23 0:36 ` Jeff King
2017-10-23 17:37 ` Stefan Beller
2017-11-03 9:32 ` Kaartic Sivaraam [this message]
2017-11-03 19:11 ` Stefan Beller
2017-11-07 12:29 ` "Cannot fetch git.git" ( iworktrees " Kaartic Sivaraam
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=0f1f8317-9d82-5e61-5332-f877ca886056@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--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).