git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-import.sh using git-fast-import

From
Nicolas Pitre <nico@cam.org>
Date
Aug 29, 2007, 15:20 UTC
Message-ID
<alpine.LFD.0.999.0708291116310.16727@xanadu.home>
In-Reply-To
<20070829041120.GA25779@coredump.intra.peff.net>
On Wed, 29 Aug 2007, Jeff King wrote:
Show 10 quoted lines
> 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
Previous: Johannes Gilger
Message 3 of 3 in “git-import.sh using git-fast-import”
  1. Nguyen Thai Ngoc DuyAug 27, 2007
  2. Johannes GilgerAug 27, 2007
  3. Nicolas PitreAug 29, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.