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

Re: [PATCH 0/3] switch to tombstone-free khashl table

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 19, 2024, 21:31 UTC
Message-ID
<xmqqy19959b2.fsf@gitster.g>
In-Reply-To
<xmqqy1a4ao3t.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
Show 14 quoted lines
> Eric Wong <e@80x24.org> writes:
>
>> The memory improvement is minor, but any memory reduction at all
>> is welcome at this point.  Fortunately, this set of changes is
>> unintrusive.
>>
>> I have some other ideas that I'll hopefully get to implement before
>> swapping kills all my SSDs (see bottom).
>
> Please describe what this topic aims at to sell the topic better.
> Are we trying to reduce memory footprint?  In other words, if this
> topic were to hit a released version of Git, what would the short
> paragraph description for the topic in the release notes look like?
> ...

So, did anything happened since this exchange? I remember that we caught and fixed a few minor sparse errors, but other than that, I am not sure what to do with this topic.

Not that I want to merge loud tree-wide topics down during the prerelease period...

Thanks.
Previous: Junio C HamanoNext: Eric Wong
Message 10 of 11 in “switch to tombstone-free khashl table”
  1. 0/3 switch to tombstone-free khashl tableEric Wong, Mar 25, 2024
  2. 1/3 list-objects-filter: use kh_size APIEric Wong, Mar 25, 2024
  3. 2/3 treewide: switch to khashl for memory savingsEric Wong, Mar 25, 2024
  4. Junio C HamanoMar 26, 2024
  5. Jeff KingMar 27, 2024
  6. Junio C HamanoMar 27, 2024
  7. 3/3 khashl: fix ensemble lookups on empty tableEric Wong, Mar 25, 2024
  8. 4/3 switch to khashl ensembleEric Wong, Mar 25, 2024
  9. Junio C HamanoMar 26, 2024
  10. Junio C HamanoApr 19, 2024
  11. Eric WongApr 19, 2024

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.