From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 60474@debbugs.gnu.org, orgmode@tec.tecosaur.net
Subject: bug#60474: 30.0.50; `write-region-inhibit-fsync' and copy-on-write file systems
Date: Sun, 01 Jan 2023 22:07:03 +0200 [thread overview]
Message-ID: <83lemm2f4o.fsf@gnu.org> (raw)
In-Reply-To: <87r0we5bqo.fsf@localhost> (message from Ihor Radchenko on Sun, 01 Jan 2023 18:51:59 +0000)
> Cc: Timothy <orgmode@tec.tecosaur.net>
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Sun, 01 Jan 2023 18:51:59 +0000
>
> We are currently exploring performance of frequent file writes in Emacs.
> This is important in org-persist library when we need to cache large
> number of data pieces, writing them on disk.
>
> It turns out that Emacs is pretty slow when writing hundreds of files:
>
> (benchmark-run-compiled
> 1000
> (with-temp-file "/tmp/test"
> (insert "test"))) ; => 4 sec
>
> Mostly because of fsync:
>
> (benchmark-run-compiled
> 1000
> (let ((write-region-inhibit-fsync t))
> (with-temp-file "/tmp/test"
> (insert "test")))) ; => 0.15 sec
>
> Timothy have found the following comment in src/fileio.c:
>
> /* fsync can be a significant performance hit. Often it doesn't
> suffice to make the file-save operation survive a crash. For
> batch scripts, which are typically part of larger shell commands
> that don't fsync other files, its effect on performance can be
> significant so its utility is particularly questionable.
> Hence, for now by default fsync is used only when interactive.
>
> For more on why fsync often fails to work on today's hardware, see:
> Zheng M et al. Understanding the robustness of SSDs under power fault.
> 11th USENIX Conf. on File and Storage Technologies, 2013 (FAST '13), 271-84
> https://www.usenix.org/system/files/conference/fast13/fast13-final80.pdf
>
> For more on why fsync does not suffice even if it works properly, see:
> Roche X. Necessary step(s) to synchronize filename operations on disk.
> Austin Group Defect 672, 2013-03-19
> https://austingroupbugs.net/view.php?id=672 */
> write_region_inhibit_fsync = noninteractive;
>
> Although fsync may provide some benefit on generic file systems, it does
> not look like it is any useful in copy-on-write file systems.
>
> I am wondering if Emacs could detect file system when writing the file
> and disable fsync for FSes like BTRFS and other CoW file systems.
Paul, any comments?
next prev parent reply other threads:[~2023-01-01 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 18:51 bug#60474: 30.0.50; `write-region-inhibit-fsync' and copy-on-write file systems Ihor Radchenko
2023-01-01 20:07 ` Eli Zaretskii [this message]
2023-01-02 3:21 ` Paul Eggert
2023-01-02 5:54 ` Ihor Radchenko
2023-01-02 12:23 ` Eli Zaretskii
2023-01-02 12:12 ` Eli Zaretskii
2023-01-02 19:38 ` Paul Eggert
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=83lemm2f4o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60474@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.