git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kjetil Barvik <barvik@broadpark.no>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Kjetil Barvik <barvik@broadpark.no>
Subject: [PATCH/RFC v1 0/2] The ext4 filesystem and racy git
Date: Sun, 15 Feb 2009 20:46:13 +0100	[thread overview]
Message-ID: <cover.1234720401.git.barvik@broadpark.no> (raw)

Ext4 is marked stable in Linux v2.6.28, and I have done a very simple
test on one disk-partition of my slow laptop, and the numbers look
very promising.

With default created ext3 disk-partition on my harddisk the 'git
checkout -q my-v2.6.25/27' test takes around 20 seconds real time for
the best cases.  The same test run on a ext4 partition takes around 14
seconds for the best cases.

And, since ext4 supports nanosecond timestamps, when I added patch
2/2, the checkout time is much more stable and more close to 14-15
seconds most of the time.

Conclusion: for GIT on my laptop the ext4 filesystem is a speedup!

>From '/proc/mounts' here is the mount options:

  /dev/hda10 /home ext3 rw,noatime,errors=continue,data=ordered 0 0
  /dev/hda12 /opt2 ext4 rw,noatime,barrier=1,journal_async_commit,data=ordered 0 0

/dev/hda10 is formatted with default (gentoo) ext3 parameters, and the
/dev/hda12 is formatted with:

  /sbin/mkfs -t ext4 -I 256 -G 64 -Oflex_bg,uninit_bg /dev/hda12


Kjetil Barvik (2):
  fix compile error when USE_NSEC is defined
  make USE_NSEC work as expected

 builtin-fetch-pack.c |    4 +-
 cache.h              |    6 ++--
 read-cache.c         |   70 ++++++++++++++++++++++++++++++++++++++++----------
 3 files changed, 61 insertions(+), 19 deletions(-)

             reply	other threads:[~2009-02-15 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15 19:46 Kjetil Barvik [this message]
2009-02-15 19:46 ` [PATCH/RFC v1 1/2] fix compile error when USE_NSEC is defined Kjetil Barvik
2009-02-15 19:46 ` [PATCH/RFC v1 2/2] make USE_NSEC work as expected Kjetil Barvik

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=cover.1234720401.git.barvik@broadpark.no \
    --to=barvik@broadpark.no \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).