Re: A 2025 NewYear present: make dpkg --force-unsafe-io the default?

[Bálint Réczey <balint@balintreczey.hu>]

Hi,

Marc Haber <mh+debian-devel@zugschlus.de> ezt írta (időpont: 2024.
dec. 31., K, 18:44):
>
> On Tue, Dec 31, 2024 at 10:32:09AM -0700, Soren Stoutner wrote:
> > On my system, which has a Western Digital Black SN850X NVMe (PCIe 4) formatted
> > ext4, dpkg runs really fast (and feels like it runs faster than it did a few
> > years ago on similar hardware).  There has been much talk on this list about
> > performance penalties with dpkg’s current configuration, and some requests for
> > actual benchmark data showing those performance penalties.
>
> Doing fsyncs to often after tiny writes will also cause write
> amplification on the SSD.
>
> I should use eatmydata more often.

I also use eatmydata time to time where it is safe, but sometimes I
forget, this is why I packaged the snippet to make all apt runs use
eatmydata automatically:
https://salsa.debian.org/debian/apt-eatmydata/-/blob/master/debian/control?ref_type=heads

I'll upload it when apt also gets a necessary fix to make removing the
snippet safe:
https://salsa.debian.org/apt-team/apt/-/merge_requests/419

There is an equivalent simple solution for GitHub Actions as well:
https://github.com/marketplace/actions/apt-eatmydata

I'll write a short blog post about those when apt-eatmydata gets
accepted to the archive.

Happy New Year!

Cheers,
Balint