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

ns/batch-fsync (Mon Apr 4, 2022)

From
NSNeeraj Singh <nksingh85@gmail.com>
Date
Apr 4, 2022, 23:20 UTC
Message-ID
<20220404232014.GA75@neerajsi-x1.localdomain>
In-Reply-To
<xmqqilropo3z.fsf@gitster.g>
On Mon, Apr 04, 2022 at 01:53:04PM -0700, Junio C Hamano wrote:
Show 22 quoted lines
> * ns/batch-fsync (2022-03-30) 14 commits
>  - core.fsyncmethod: performance tests for batch mode
>  - t/perf: add iteration setup mechanism to perf-lib
>  - core.fsyncmethod: tests for batch mode
>  - test-lib-functions: add parsing helpers for ls-files and ls-tree
>  - core.fsync: use batch mode and sync loose objects by default on Windows
>  - unpack-objects: use the bulk-checkin infrastructure
>  - update-index: use the bulk-checkin infrastructure
>  - builtin/add: add ODB transaction around add_files_to_cache
>  - cache-tree: use ODB transaction around writing a tree
>  - core.fsyncmethod: batched disk flushes for loose-objects
>  - object-file: pass filename to fsync_or_die
>  - bulk-checkin: rebrand plug/unplug APIs as 'odb transactions'
>  - bulk-checkin: rename 'state' variable and separate 'plugged' boolean
>  - Merge branch 'ns/core-fsyncmethod' into ns/batch-fsync
> 
>  Introduce a filesystem-dependent mechanism to optimize the way the
>  bits for many loose object files are ensured to hit the disk
>  platter.
> 
>  Will merge to 'next'?
>  source: <pull.1134.v5.git.1648616734.gitgitgadget@gmail.com>
Please expect a reroll today to address the remaining issues in that thread.

Thanks, Neeraj

Previous: Junio C HamanoNext: rsbecker@nexbridge.com
Message 2 of 7 in “What's cooking in git.git (Apr 2022, #01; Mon, 4)”
  1. Junio C HamanoApr 4, 2022
  2. ns/batch-fsync (Mon Apr 4, 2022)Neeraj Singh, Apr 4, 2022
  3. rsbecker@nexbridge.comApr 4, 2022
  4. Neeraj SinghApr 5, 2022
  5. rsbecker@nexbridge.comApr 5, 2022
  6. Junio C HamanoApr 6, 2022
  7. gf/shorthand-version-and-help (was: What's cooking in git.git (Apr 2022, #01; Mon, 4))Ævar Arnfjörð Bjarmason, Apr 6, 2022

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.