Hi Nicolas, On Friday 08 February 2008 19:03, Nicolas Pitre wrote:After the suggestions in this thread I tried to experiment with the --window and --depth options of git-repack, and indeed, there are still reserves. So far I'm at 2G (saved 500M), unfortunately the aggressive values like --window=250 --depth=250 that someone mentioned here cause out-of-memory on a machine with 8G :-( If there's anybody brave enough here to try as well, I'd be grateful. Maybe it would be also interesting to _exactly_ locate what causes the oom, and eg. exclude the object from the pack if possible. The tree is available here: git clone git://o3-build.services.openoffice.org/git/ooo.git git clone http://o3-build.services.openoffice.org/~svn/ooo.git (the same over http://) Thank you in advance! Regards, Jan - 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
| Justin C. Sherrill | Re: dragonflybsd.org website link? |
| David Woodhouse | Re: -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Eric Sandeen | Re: [RFC] Heads up on sys_fallocate() |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Patrick McHardy | [NET_SCHED 01/15]: sch_atm: fix format string warning |
