Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Debootstrap is used in Debian ISO installer (debian-installer, d-i) for initial target rootfs bootstrapping. With sync enabled, this takes hundreds of minutes to unpack and configure base system on a HDD. With eatmydata it takes about a minute. What could be done to introduce eatmydata into

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Version: 1.0.115 Hi everyone, I’m appalled that this feature request is still open… I’ve got a need to do this without patching debootstrap, and have had success (although I did not time it, but someone else can ;-) with this sequence of commands (assuming dpkg-deb is available ― which my

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Hi, On Sat, 16 Feb 2013 16:54:52 -0700 Bob Proulx wrote: > I have also been suffering with the much slower dpkg on Sid. Today I > performed a test of a default debootstrap chroot and had this > benchmark data. I am using a local full mirror so that network > performance is not

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

On Mon, Apr 01, 2013 at 10:14:16AM -0400, Phillip Susi wrote: On 3/31/2013 4:17 PM, Marc Haber wrote: The following patch introduces an --include-early option which allows to introduce eatmydata early enough: Is this intended to be applied instead of, or on top of my initial patch? If

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/31/2013 4:17 PM, Marc Haber wrote: The following patch introduces an --include-early option which allows to introduce eatmydata early enough: Is this intended to be applied instead of, or on top of my initial patch? If the former ( which I'm

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Debootstrap is very, very slow. I watched a server install crawl by for something like an hour at a rate of about 1 package per second. A simple debootstrap chroot takes 10 minutes to setup, with a predownloaded tarball. This slowness is due to dpkg making excessive use of fsync(). Requests

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Phillip Susi wrote: After patching debootstrap to add eatmydata to the required list, and activate it during the second stage install, the time to construct the chroot dropped from 10m to 2m. This should also make installing new systems MUCH faster. I have also been suffering with the much

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2013 06:54 PM, Bob Proulx wrote: # time debootstrap wheezy testinstall http://localmirror/ftp.us.debian.org/debian ... real2m58.577s user0m49.639s sys 0m8.749s Wow, that's pretty fast. I was testing on a server with a raid5

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Phillip Susi wrote: Bob Proulx wrote: # time debootstrap wheezy testinstall http://localmirror/ftp.us.debian.org/debian ... real2m58.577s user0m49.639s sys 0m8.749s Wow, that's pretty fast. 2m58s was the slow time. 1m4.819s was the fast time. :-) I was testing on a server

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: debootstrap Version: 1.0.46 Debootstrap is very, very slow. I watched a server install crawl by for something like an hour at a rate of about 1 package per second. A simple debootstrap chroot takes 10 minutes to setup, with a predownloaded

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

Phillip Susi ps...@ubuntu.com (15/02/2013): This should also make installing new systems MUCH faster. FWIW: | base-installer (1.121) unstable; urgency=low | | [ Colin Watson ] | * Merge from Ubuntu: | - Run dpkg with --force-unsafe-io during installation; syncing is | unnecessary

Bug#700633: Debootstrap is very slow. Please use eatmydata to fix this.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/15/2013 09:09 PM, Cyril Brulebois wrote: - --force-unsafe-io only eliminates *some* of the syncs, and seems to only be applied in the latter part of the installation that takes place after debootstrap. I started working on a patch to dpkg to