From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Git Mailing List <git@vger.kernel.org>, Chris Lee <clee@kde.org>
Subject: Re: kde.git is now online
Date: Thu, 05 Apr 2007 15:45:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704051532240.28181@xanadu.home> (raw)
In-Reply-To: <alpine.LFD.0.98.0704051334590.28181@xanadu.home>
On Thu, 5 Apr 2007, Nicolas Pitre wrote:
> On Thu, 5 Apr 2007, Linus Torvalds wrote:
>
> >
> >
> > On Thu, 5 Apr 2007, H. Peter Anvin wrote:
> > >
> > > http://userweb.kernel.org/~hpa/kdegit/
> > >
> > > It's available both as a tarball and as an expanded tree.
> >
> > Thanks. Am downloading it right now ("0% 146.99kB/s" - it will take quite
> > some time ;)
>
> I'm downloading it too (794.3 KB/s).
OK this is a really nice test repo. I have only 1 GB of ram, and
although basic operations appear to work just fine, this data set shows
its weight in some ways.
For example I think there might be ways to improve the pack mmap
windowing, or git-fsck's IO patterns. For example, git-fsck --full
spend 96% of the time waiting for IO completion and only 4% actually
performing some work according to top. At that rate that makes fsck
--full rather unusable on this repo. Without --full then fsck completes
in less than 2 seconds.
Nicolas
next prev parent reply other threads:[~2007-04-05 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 17:03 kde.git is now online H. Peter Anvin
2007-04-05 17:30 ` Linus Torvalds
2007-04-05 17:38 ` Nicolas Pitre
2007-04-05 19:45 ` Nicolas Pitre [this message]
2007-04-05 20:51 ` Linus Torvalds
2007-04-05 22:00 ` Nicolas Pitre
2007-04-06 1:24 ` Linus Torvalds
2007-04-05 18:03 ` Chris Lee
2007-04-05 21:26 ` Junio C Hamano
2007-04-06 11:32 ` Geert Bosch
2007-04-06 12:59 ` Nicolas Pitre
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=alpine.LFD.0.98.0704051532240.28181@xanadu.home \
--to=nico@cam.org \
--cc=clee@kde.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--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).