Re: [PATCH v2 0/3] A design for future-proofing fsync() configuration
From: Neeraj Singh <hidden>
Date: 2021-12-08 00:44:23
From: Neeraj Singh <hidden>
Date: 2021-12-08 00:44:23
On Tue, Dec 7, 2021 at 3:57 AM Patrick Steinhardt [off-list ref] wrote:
While I bail from the question of whether we want to grant as much configurability to the user as this patch series does, I quite like the implementation. It feels rather straight-forward and it's easy to see how to extend it to support syncing of other subsystems like the loose refs. Thanks! Patrick
Thanks for the positive comment. I'm assuming that a major Git services like GitHub or GitLab would be able to take advantage of the granular options and knowledge of their hosting environment to choose the right values for any server-side git deployments. I'd probably turn off syncing for derived stuff like the commit-graph file and pack metadata. My underlying interest in all of these changes is to make Windows stop looking so bad (we're defaulting to core.fsyncobjectfiles=true). Batch mode should give similar safety and much more optimizable performance in our environment. Thanks, Neeraj