From: Kjetil Barvik <barvik@broadpark.no>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Git Mailing List <git@vger.kernel.org>,
spearce@spearce.org
Subject: Re: [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid
Date: Mon, 27 Apr 2009 17:58:17 +0200 [thread overview]
Message-ID: <86skjudr6u.fsf@broadpark.no> (raw)
In-Reply-To: <alpine.LFD.2.00.0904270757410.22156@localhost.localdomain>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Sun, 26 Apr 2009, Junio C Hamano wrote:
>> I like the end result.
>>
>> But I am not sure about dropping the nanosecond resolution timestamps.
>> The area was extended recently in preparation for ext4; we can take
>> advantage of it to reduce the chance the racy-git avoidance codepath
>> triggers if we keep it.
>>
>> fba2f38 (make USE_NSEC work as expected, 2009-02-19)
>>
>> c06ff49 (Record ns-timestamps if possible, but do not use it without
>> USE_NSEC, 2009-03-04)
>
> Hey, we can leave the NSEC support in. Admittedly removing that was about
> half the patch, but even with it left in, it would be a cleanup.
I think we should have the NSEC support, as it is a performance
impromvent, at least on my laptop. OK, not a huge improvment, but
still.
For git version 1.6.3.rc3 I made a litle test, and the difference was
the following for the 'git checkout my-v2.6.25' (from my-v2.6.27):
for git compiled with for git compiled without
'make USE_NSEC=1 ...': the 'USE_NSEC=1' part:
OK open calls: 13872 14386
OK close calls: 13872 14386
OK mmap2 calls: 102 649
OK munmap calls: 61 608
so, an improvment of 514 open() and close() calls, and 547 mmap2() and
munmap() calls, for this particular test on my particular slow laptop
disk.
As I wrote in fba2f38 I would guess that the improvment is larger for
a faster disk, and a SSD disk should be able to see a larger
improvment that I did above.
-- kjetil
next prev parent reply other threads:[~2009-04-27 15:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 10:55 [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid Robin Rosenberg
2009-04-26 11:06 ` Robin Rosenberg
2009-04-26 12:06 ` [PATCH 1/2] Silence diffs due to use by non-C code Robin Rosenberg
2009-04-26 18:38 ` [PATCH] Add core.trustlowlevelstat for diffs in dev,ino,uid and gid Junio C Hamano
2009-04-26 19:25 ` Linus Torvalds
2009-04-26 22:02 ` Robin Rosenberg
2009-04-27 6:55 ` Junio C Hamano
2009-04-27 15:00 ` Linus Torvalds
2009-04-27 15:58 ` Kjetil Barvik [this message]
2010-03-14 20:51 ` Robin Rosenberg
2010-03-15 6:50 ` Junio C Hamano
2010-03-15 7:41 ` Alex Riesen
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=86skjudr6u.fsf@broadpark.no \
--to=barvik@broadpark.no \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.org \
--cc=torvalds@linux-foundation.org \
/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).