git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 4/4] gc --aggressive: three phase repacking

From
Duy Nguyen <pclouds@gmail.com>
Date
Mar 19, 2014, 11:03 UTC
Message-ID
<CACsJy8BVmc0K5Rdr_putTQM5Hs2agizyW8cxAPFLb0LnXntG7Q@mail.gmail.com>
In-Reply-To
<CACsJy8CU3JyL74OuurjDr5-FHmBOCRahtXukukCqGx1cTdjvMQ@mail.gmail.com>
On Tue, Mar 18, 2014 at 12:00 PM, Duy Nguyen <pclouds@gmail.com> wrote:
Show 12 quoted lines
>>>             size  time
>>> old aggr.   36MB  5m51
>>> new aggr.   37MB  6m13
>>> repack -adf 48MB  1m12
>>
>> I am not clear on what these times mean. It looks like the new code is
>> slower _and_ bigger. Can you explain them?
>
> That's right :) The upside is faster operations, which is complely
> missed here. The good thing from those numbers is pack size does not
> increase much (the upper limit would be repack -adf with default
> settings).
Something is not right. The performance numbers are against me. Still looking..
-- 
Duy
Previous: David KastrupNext: Jeff King
Message 14 of 21 in “Better "gc --aggressive"”
  1. 0/4 Better "gc --aggressive"Nguyễn Thái Ngọc Duy, Mar 16, 2014
  2. 1/4 environment.c: fix constness for odb_pack_keep()Nguyễn Thái Ngọc Duy, Mar 16, 2014
  3. index-pack: do not segfault when keep_name is NULLNguyễn Thái Ngọc Duy, Mar 16, 2014
  4. 2/4 pack-objects: support --keepNguyễn Thái Ngọc Duy, Mar 16, 2014
  5. 3/4 gc --aggressive: make --depth configurableNguyễn Thái Ngọc Duy, Mar 16, 2014
  6. 4/4 gc --aggressive: three phase repackingNguyễn Thái Ngọc Duy, Mar 16, 2014
  7. Junio C HamanoMar 17, 2014
  8. Duy NguyenMar 17, 2014
  9. Junio C HamanoMar 17, 2014
  10. Jeff KingMar 18, 2014
  11. Duy NguyenMar 18, 2014
  12. Jeff KingMar 18, 2014
  13. David KastrupMar 18, 2014
  14. Duy NguyenMar 19, 2014
  15. Jeff KingMar 18, 2014
  16. Duy NguyenMar 18, 2014
  17. Duy NguyenMar 18, 2014
  18. David KastrupMar 18, 2014
  19. David KastrupMar 18, 2014
  20. Duy NguyenMar 16, 2014
  21. Duy NguyenMar 20, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.