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

Re: Some git performance measurements..

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 8, 2007, 11:05 UTC
Message-ID
<Pine.LNX.4.64.0712081103430.27959@racer.site>
In-Reply-To
<e2b179460712071115k369dddcatb0f6456d0028acbb@mail.gmail.com>
Hi,
On Fri, 7 Dec 2007, Mike Ralphson wrote:
Show 24 quoted lines
> On Dec 7, 2007 6:37 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Fri, 7 Dec 2007, Mike Ralphson wrote:
> >
> > > On Dec 7, 2007 1:49 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > > On Fri, 7 Dec 2007, Mike Ralphson wrote:
> > > >
> > > > > I benchmarked 3 alternative qsorts, qsortG [2] was the fastest 
> > > > > on my system but has funky licensing, the NetBSD qsort was 
> > > > > middle-range and the glibc one the slowest of the three (but 
> > > > > that could be due to it being tuned for a "Sun 4/260"). All of 
> > > > > them show over 100x speed improvements on a git-status of my 
> > > > > main repo (104s -> ~0.7s)
> > > >
> >
> > Okay, sorry, I did not bother reading further when I read "You may use 
> > it in anything you like;".
> >
> > But if the author did not respond, it might be a better idea to just 
> > reimplement it.
> >
> 
> I've just tried the mergesort implementation as used in msysgit and that 
> performs faster for me. It's simpler, and compatibly licensed. It looks 
> good.

Now I'm confused. You said you tested qsortG, NetBSD qsort and qlibc, with glibc performing the slowest. Now, 4msysgit's implementation is based on glibc (Thanks Brian!), so I wonder if you could redo the performance tests and say if qsortG still is substantially faster than 4msysgit's qsort?

Ciao, Dscho

Previous: Mike RalphsonNext: Brian Downing
Message 21 of 28 in “Some git performance measurements..”
  1. Linus TorvaldsNov 29, 2007
  2. Linus TorvaldsNov 29, 2007
  3. Nicolas PitreNov 29, 2007
  4. Linus TorvaldsNov 29, 2007
  5. Nicolas PitreNov 29, 2007
  6. Linus TorvaldsNov 29, 2007
  7. Nicolas PitreNov 29, 2007
  8. Junio C HamanoNov 30, 2007
  9. Linus TorvaldsNov 30, 2007
  10. Jakub NarebskiNov 30, 2007
  11. Linus TorvaldsNov 30, 2007
  12. Jakub NarebskiNov 30, 2007
  13. Nicolas PitreNov 30, 2007
  14. Steffen ProhaskaNov 30, 2007
  15. Mike RalphsonDec 7, 2007
  16. Johannes SchindelinDec 7, 2007
  17. Linus TorvaldsDec 7, 2007
  18. Mike RalphsonDec 7, 2007
  19. Johannes SchindelinDec 7, 2007
  20. Mike RalphsonDec 7, 2007
  21. Johannes SchindelinDec 8, 2007
  22. Brian DowningDec 8, 2007
  23. Linus TorvaldsNov 30, 2007
  24. Federico Mena QuinteroDec 5, 2007
  25. Joachim B HagaDec 1, 2007
  26. Linus TorvaldsDec 1, 2007
  27. Junio C HamanoNov 29, 2007
  28. per-directory-exclude: lazily read .gitignore filesJunio C Hamano, Nov 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.