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
