Nicolas Pitre, Thu, Jul 10, 2008 18:21:09 +0200: > On Thu, 10 Jul 2008, Junio C Hamano wrote: > > (2) exploding memory use, suspected to be due to malloc pool > > fragmentation under multithreading. ... > > but I do not > > recall the latter issue has been addressed. > > Well, for "standard" repositories such as the Linux kernel, things > always worked just fine. And commit eac12e2d is apparently helping a > lot with the remaining odd cases. And if someone has problems due to > this then a simple 'git config --global pack.threads 1' would restore > the non threaded behavior. Have you ever seen what happens to Windows XP on memory shortage? It freezes *hard*. Not a good behaviour for _default_ settings. And if someone has no problems with memory, then a simple "git config pack.threads 100" would restore the threaded behaviour for a repository which supposedly will never grow up. -- 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
