From cd37cab10bf875a2ccb4886f6a7f624aa28c27d2 Mon Sep 17 00:00:00 2001 From: Petter Reinholdtsen Date: Fri, 25 Nov 2016 14:49:35 +0100 Subject: [PATCH] Publish post. --- blog/data/2016-11-25-d-i-eatmydata.txt | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/blog/data/2016-11-25-d-i-eatmydata.txt b/blog/data/2016-11-25-d-i-eatmydata.txt index 9c2802cb8b..061b52e0f6 100644 --- a/blog/data/2016-11-25-d-i-eatmydata.txt +++ b/blog/data/2016-11-25-d-i-eatmydata.txt @@ -3,18 +3,18 @@ Tags: english, debian, debian edu Date: 2016-11-25 14:50

Two years ago, I did some experiments with eatmydata and the Debian -installer, observing how using +installation system, observing how using eatmydata could speed up the installation quite a bit. My testing measured speedup around 20-40 percent for Debian Edu, where we install around -1000 packages from within the installer. The eatmydata package is a -way to disable/delay file system flushing. This is a bit risky in the -general case, as files that should be stored on disk will stay only in -memory a bit longer than expected, causing problems if a machine -crashes at an inconvenient time. But for an installation, if the -machine crashes during installation the process is normally restarted, -and avoiding disk operations as much as possible to speed up the -process make perfect sense. +1000 packages from within the installer. The eatmydata package +provide a way to disable/delay file system flushing. This is a bit +risky in the general case, as files that should be stored on disk will +stay only in memory a bit longer than expected, causing problems if a +machine crashes at an inconvenient time. But for an installation, if +the machine crashes during installation the process is normally +restarted, and avoiding disk operations as much as possible to speed +up the process make perfect sense.

I added code in the Debian Edu specific installation code to enable eatmydata, -- 2.47.2