{"thread":{"id":"22106","subject":"gc.auto bug in 1.6.5.7","startedAt":"2010-01-06T17:59:28Z","lastAt":"2010-01-06T22:27:15Z","messageCount":3,"participants":["Jon Nelson","Brandon Casey"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"130933","messageId":"cccedfc61001060959h72a07eb6g78f2ca231867df63@mail.gmail.com","threadId":"22106","inReplyTo":null,"subject":"gc.auto bug in 1.6.5.7","fromName":"Jon Nelson","fromEmail":"jnelson@jamponi.net","sentAt":"2010-01-06T17:59:28Z","receivedAt":"2010-01-06T17:59:28Z","isPatch":false,"sender":{"key":"jnelson@jamponi.net","avatar":null},"body":"It would appear that there is a bug in git, at least as of 1.6.5.7, in\nthe gc command.\nWhen gc.auto is non-zero, it appears to consider packfiles as \"loose\"\n- this conflicts with pack.packSizeLimit, insofar as I have\npack.packSizeLimit set to 2M (which appears to work).  If gc.auto is,\nsay, 50 - once I exceed 50 2MB packs then gc --auto repacks *every\nsingle time* it is run. This is unexpected, at least.\n\n-- \nJon\n"},{"id":"130938","messageId":"u1EMnFha7hfr0SI0p8dEvAJML7vykSCAA6YzQd7klvze6oKChlMCLg@cipher.nrlssc.navy.mil","threadId":"22106","inReplyTo":"cccedfc61001060959h72a07eb6g78f2ca231867df63@mail.gmail.com","subject":"Re: gc.auto bug in 1.6.5.7","fromName":"Brandon Casey","fromEmail":"brandon.casey.ctr@nrlssc.navy.mil","sentAt":"2010-01-06T18:31:07Z","receivedAt":"2010-01-06T18:31:07Z","isPatch":false,"sender":{"key":"brandon.casey.ctr@nrlssc.navy.mil","avatar":null},"body":"Jon Nelson wrote:\n> It would appear that there is a bug in git, at least as of 1.6.5.7, in\n> the gc command.\n> When gc.auto is non-zero, it appears to consider packfiles as \"loose\"\n> - this conflicts with pack.packSizeLimit, insofar as I have\n> pack.packSizeLimit set to 2M (which appears to work).  If gc.auto is,\n> say, 50 - once I exceed 50 2MB packs then gc --auto repacks *every\n> single time* it is run. This is unexpected, at least.\n\nThere is also a gc.autopacklimit which controls auto-gc'ing based on\nthe number of packs.  The default is 50 and it does not consider the\npack.packSizeLimit setting when deciding whether or not to auto-gc.\nIt can be raised, or it can be disabled by setting it to zero.\n\nThe ideal number of packs is one, but if you limit the size of packs\nto be very small, then you will quickly grow the number of packs.\nPerhaps autogc should only count packs that are much smaller than\npack.packSizeLimit?  Looks like there is already a comment in\nbuiltin-gc.c suggesting something similar.\n\n-brandon\n"},{"id":"130958","messageId":"cccedfc61001061427k6dcb35bcw9f5b5ae0aaf52786@mail.gmail.com","threadId":"22106","inReplyTo":"u1EMnFha7hfr0SI0p8dEvAJML7vykSCAA6YzQd7klvze6oKChlMCLg@cipher.nrlssc.navy.mil","subject":"Re: gc.auto bug in 1.6.5.7","fromName":"Jon Nelson","fromEmail":"jnelson@jamponi.net","sentAt":"2010-01-06T22:27:15Z","receivedAt":"2010-01-06T22:27:15Z","isPatch":false,"sender":{"key":"jnelson@jamponi.net","avatar":null},"body":"On Wed, Jan 6, 2010 at 12:31 PM, Brandon Casey\n<brandon.casey.ctr@nrlssc.navy.mil> wrote:\n> Jon Nelson wrote:\n>> It would appear that there is a bug in git, at least as of 1.6.5.7, in\n>> the gc command.\n>> When gc.auto is non-zero, it appears to consider packfiles as \"loose\"\n>> - this conflicts with pack.packSizeLimit, insofar as I have\n>> pack.packSizeLimit set to 2M (which appears to work).  If gc.auto is,\n>> say, 50 - once I exceed 50 2MB packs then gc --auto repacks *every\n>> single time* it is run. This is unexpected, at least.\n>\n> There is also a gc.autopacklimit which controls auto-gc'ing based on\n> the number of packs.  The default is 50 and it does not consider the\n> pack.packSizeLimit setting when deciding whether or not to auto-gc.\n> It can be raised, or it can be disabled by setting it to zero.\n\nI disabled it entirely and that seemed to resolve the issue.  Thanks!\n\n\n-- \nJon\n"}]}