git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neeraj Singh <nksingh85@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ns/batch-fsync (Mon Apr 4, 2022)
Date: Mon, 4 Apr 2022 16:20:14 -0700	[thread overview]
Message-ID: <20220404232014.GA75@neerajsi-x1.localdomain> (raw)
In-Reply-To: <xmqqilropo3z.fsf@gitster.g>

On Mon, Apr 04, 2022 at 01:53:04PM -0700, Junio C Hamano wrote:
> * 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

  reply	other threads:[~2022-04-04 23:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 20:53 What's cooking in git.git (Apr 2022, #01; Mon, 4) Junio C Hamano
2022-04-04 23:20 ` Neeraj Singh [this message]
2022-04-04 23:31   ` ns/batch-fsync (Mon Apr 4, 2022) rsbecker
2022-04-05  4:35     ` Neeraj Singh
2022-04-05 12:35       ` rsbecker
2022-04-06 15:02         ` Junio C Hamano
2022-04-06  8:56 ` gf/shorthand-version-and-help (was: What's cooking in git.git (Apr 2022, #01; Mon, 4)) Ævar Arnfjörð Bjarmason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220404232014.GA75@neerajsi-x1.localdomain \
    --to=nksingh85@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).