4 ms·
Like I said.
by Brian_K_White 2y ago
Like I said.
- levkk 2y agoPretty sure kernel doesn't have to fsync on close. In fact, you don't want it to, otherwise you're limiting the performance of your page cache. So fsync on install for dpkg makes perfect sense.
- Brian_K_White 2y agoI didn't say it synced. The file is simply "written" and available at that point. It makes no sense to trust that fsync() does what it promises but not that close() does what it promises. close() promises that when close() returns, the data is stored and some other process may open() and find all of it verbatim. And that's all you care about or have any business caring about unless you are the kernel yourself.
- hiciu 2y agoI would like to introduce you to a few case studies on bugzilla: https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_is_dpkg_so_slow_when_using_new_filesystems_such_as_btrfs_or_ext4.3F https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Why_is_dpkg_so_slo...
- switch007 2y agoGet involved, tell and show them you know better. They have a bug tracker, mailing list etc