From: Nicolas Pitre <nico@cam.org>
To: Jeff King <peff@peff.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git-import.sh using git-fast-import
Date: Wed, 29 Aug 2007 11:20:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0708291116310.16727@xanadu.home> (raw)
In-Reply-To: <20070829041120.GA25779@coredump.intra.peff.net>
On Wed, 29 Aug 2007, Jeff King wrote:
> On Tue, Aug 28, 2007 at 11:47:25PM -0400, Shawn O. Pearce wrote:
>
> > Yea, so like the parallel pack-objects experiment that Nico had
> > done recently we decreased wall-clock time at the expense of using a
> > larger amount of the system resources. That is bad as we use more
> > CPU time than we saved in wallclock time. Usually a bad tradeoff,
> > unless you have a realtime requirement you have to meet.
>
> It depends. If we all have 64-core processors in a few years, then it
> might be a better tradeoff.
Depends. In the experiment I did, I clearly identified flaws showing
that the direction was bad and that another approach has to be pursued.
Thinking in terms of 64-core processors is no excuse for bad designs.
> Of course, some users might want to optimize
> for wall-clock time, while others want power consumption, etc.
Better get both at the same time when possible.
Nicolas
prev parent reply other threads:[~2007-08-29 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 16:13 git-import.sh using git-fast-import Nguyen Thai Ngoc Duy
2007-08-27 17:44 ` Johannes Gilger
[not found] ` <20070828035430.GJ18160@spearce.org>
[not found] ` <20070828055431.GA28311@coredump.intra.peff.net>
[not found] ` <20070828061118.GO18160@spearce.org>
[not found] ` <20070828063316.GB5444@coredump.intra.peff.net>
[not found] ` <20070829034725.GR18160@spearce.org>
[not found] ` <20070829041120.GA25779@coredump.intra.peff.net>
2007-08-29 15:20 ` Nicolas Pitre [this message]
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.999.0708291116310.16727@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.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).