[resend - correcting a couple of typos and addressing git@vger correctly - apologies] On 5/3/07, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote: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. 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_bui... 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. cheers m - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Gabriel C | Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | [GIT]: Networking |
| Thomas Jarosch | Re: TCP connection stalls under 2.6.24.7 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
