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

Re: Git benchmarks at OpenOffice.org wiki

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
May 6, 2007, 20:05 UTC
Message-ID
<200705062205.34814.robin.rosenberg.lists@dewire.com>
In-Reply-To
<46a038f90705030348o260fbe6cwc92d07778269c937@mail.gmail.com>
torsdag 03 maj 2007 skrev Martin Langhoff:
Show 17 quoted lines
> [resend - correcting a couple of typos and addressing git@vger
> correctly - apologies]
> 
> On 5/3/07, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> > The reason is simple. I have a lousy one gigabyte RAM only, while
> > git wants 1.7GB virtual to do the diff-stat.  and 800 MB resident. The swap is having a party,
> 
> That is true, unfortunately. git will fly if it can fit its working
> set plus the kernel stat cache for your working tree in memory. And
> the underlying assumption is that for large trees you'll have gobs of
> RAM. If things don't fit, it does get rather slow...
> 
> But... just to put things in perspective, how long does it take to
> *compile* that checkout on that same laptop. I remember reading
> instructions to the tune of "don't even try to compile this with less
> than 4GB RAM, a couple of CPUs and 12hs". Those were for the OSX build
> IIRC.

No idea. I wouldn't try it without distcc and ccache anyway which makes the capabilities of this particular machine less relevant.

Show 6 quoted lines
> Ah - it's moved to the general instructions: "Building OOo takes some
> time (approx 10-12 hours on standard desktop PC) ":
> http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org#Starting_the_real_build
> 
> So I don't think anyone working on projects the size of the kernel or
> OO.org is going to be happy with 1GB RAM.

The kernel 2.6 repo isn't in the same ball park wrt to size. Hacking the kernel is quite fine on this machine and even smaller though the first compile takes some time. Having more is always fun though.

Consider another huge project like Eclipse. Similar operations take a loong time (not anywhere near the eons that CVS need, but...) and building Eclipse with 1GB i very reasonable so sheer project size does not per se demand powerful computers. KDE is another huge project that is reasonable to build with 1GB. The first time is somewhat painful, but rebuilding is not.

-- robin
Previous: Martin LanghoffNext: Jakub Narebski
Message 35 of 36 in “Git benchmarks at OpenOffice.org wiki”
  1. Jakub NarebskiMay 1, 2007
  2. Junio C HamanoMay 1, 2007
  3. Andy ParkinsMay 2, 2007
  4. Julian PhillipsMay 2, 2007
  5. Andy ParkinsMay 2, 2007
  6. Julian PhillipsMay 2, 2007
  7. Andy ParkinsMay 2, 2007
  8. Julian PhillipsMay 2, 2007
  9. Jan HolesovskyMay 2, 2007
  10. Andy ParkinsMay 2, 2007
  11. Junio C HamanoMay 2, 2007
  12. Johannes SchindelinMay 2, 2007
  13. Jakub NarebskiMay 2, 2007
  14. Johannes SchindelinMay 2, 2007
  15. Linus TorvaldsMay 5, 2007
  16. Junio C HamanoMay 7, 2007
  17. Linus TorvaldsMay 7, 2007
  18. Jan HolesovskyMay 2, 2007
  19. Johannes SchindelinMay 2, 2007
  20. Jan HolesovskyMay 2, 2007
  21. Johannes SchindelinMay 2, 2007
  22. Petr BaudisMay 2, 2007
  23. Jan HolesovskyMay 2, 2007
  24. Petr BaudisMay 2, 2007
  25. Petr BaudisMay 2, 2007
  26. Jakub NarebskiMay 2, 2007
  27. Jan HolesovskyMay 3, 2007
  28. Alex RiesenMay 3, 2007
  29. Johannes SixtMay 3, 2007
  30. Jakub NarebskiMay 4, 2007
  31. Florian WeimerMay 3, 2007
  32. Johannes SchindelinMay 3, 2007
  33. Robin RosenbergMay 3, 2007
  34. Martin LanghoffMay 3, 2007
  35. Robin RosenbergMay 6, 2007
  36. Jakub NarebskiMay 3, 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.