From: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>, darcs-devel@darcs.net
Subject: Re: Re: Darcs-git pulling from the Linux repo: a Linux VM question
Date: Wed, 27 Apr 2005 17:54:32 +0200	[thread overview]
Message-ID: <7iu0lskyfb.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0504270823480.18901@ppc970.osdl.org> (Linus Torvalds's message of "Wed, 27 Apr 2005 08:31:37 -0700 (PDT)")
>> For now, does anyone know how I can tune the Linux VM to get a 720
>> MB process to run reliably in 640 MB of main memory?
> I really think you're screwed.
Thanks, that's what I needed to know.
> You _really_ shouldn't read in files that you don't absolutely need.
Ahem... you don't expect me to embark on hacking Git without at least
understanding that, do you?
> That's really the biggest point of git: using the sha1 for naming the
> objects is really all about "descrive the contents using 20 bytes instead
> of by reading the contents".
Here we're speaking about the initial import.  Committed on 17 April
2005 by Linus Torvalds, with the comment ``Let it rip''.  220 MB of
changed files in a single commit.  2 minutes real time just to read
all the files, never mind doing anything useful with them.
To put it mildly, Darcs is not optimised for that sort of usage.
> Sorry.  You really need to fix darcs.
That's exactly why we're so interested in your repository.
                                        Juliusz
next prev parent reply	other threads:[~2005-04-27 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 13:10 Darcs-git pulling from the Linux repo: a Linux VM question Juliusz Chroboczek
2005-04-27 15:31 ` Linus Torvalds
2005-04-27 15:54   ` Juliusz Chroboczek [this message]
2005-04-27 16:16     ` Linus Torvalds
2005-04-28 11:39       ` [darcs-devel] " David Roundy
2005-04-28 15:36         ` Juliusz Chroboczek
2005-04-29 11:25           ` David Roundy
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=7iu0lskyfb.fsf@lanthane.pps.jussieu.fr \
    --to=juliusz.chroboczek@pps.jussieu.fr \
    --cc=darcs-devel@darcs.net \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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).