torsdag 03 maj 2007 skrev Martin Langhoff: > [resend - correcting a couple of typos and addressing git@vger > correctly - apologies] > > On 5/3/07, Robin Rosenberg <robin.rosenberg.lists@xxxxxxxxxx> 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. > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html