Your message dated Mon, 27 Jun 2016 11:11:57 +0200 with message-id <20160627111022.GA7477@debian.org> and subject line Re: Bug#576649: [apt]: Very slow apt-get update has caused the Debian Bug report #576649, regarding [apt]: Very slow apt-get update to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 576649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576649 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [apt]: Very slow apt-get update
- From: Jens Seidel <jensseidel@users.sf.net>
- Date: Tue, 6 Apr 2010 10:23:57 +0200
- Message-id: <20100406082357.GA6159@merkur.sol.de>
Package: apt Version: 0.7.25.3 Calling apt-get update on my OpenMoko phone (armel, 128MB RAM, sd card) takes forever: Ign http://pkg-fso.alioth.debian.org unstable/main Sources Ign http://pkg-fso.alioth.debian.org unstable/main Packages Ign http://pkg-fso.alioth.debian.org unstable/main Sources Hit http://pkg-fso.alioth.debian.org unstable/main Packages Hit http://pkg-fso.alioth.debian.org unstable/main Sources Hit http://ftp2.de.debian.org unstable Release.gpg Hit http://ftp2.de.debian.org experimental Release.gpg Hit http://ftp2.de.debian.org unstable Release Hit http://ftp2.de.debian.org experimental Release Hit http://ftp2.de.debian.org unstable/main Packages Get:1 http://ftp2.de.debian.org unstable/main Sources [3852kB] Get:2 http://ftp2.de.debian.org experimental/main Packages [209kB] Get:3 http://ftp2.de.debian.org experimental/main Sources [108kB] Fetched 3B in 2h 39min 45s (0B/s) The next time (a few days later) I got: Fetched 10.8MB in 1h 52min 43s (1,598B/s) Reading package lists... Done The device is not the fastest but the CPU was idle all the time (2-3% used by bzip2) and I also doubt that IO (which is a bottleneck) is sooo slow. At least it should not need more than 2 hours to download 3B (this values is very very likely wrong). The internet connection should be limited by 200-300kB/s. Any idea how to speed it up? I deactivated already downloading package file diffs. Jens
--- End Message ---
--- Begin Message ---
- To: 576649-done@bugs.debian.org
- Subject: Re: Bug#576649: [apt]: Very slow apt-get update
- From: Julian Andres Klode <jak@debian.org>
- Date: Mon, 27 Jun 2016 11:11:57 +0200
- Message-id: <20160627111022.GA7477@debian.org>
- In-reply-to: <20100411175241.GB29631@merkur.sol.de>
- References: <20100406082357.GA6159@merkur.sol.de> <g2sc64043e61004061020t2c4e9dc8r1320366b6ca20e1c@mail.gmail.com> <20100407001648.GA7701@merkur.sol.de> <20100411175241.GB29631@merkur.sol.de>
On Sun, Apr 11, 2010 at 07:52:44PM +0200, Jens Seidel wrote: > On Wed, Apr 07, 2010 at 02:16:50AM +0200, Jens Seidel wrote: > > On Tue, Apr 06, 2010 at 07:20:51PM +0200, David Kalnischkies wrote: > > > 2010/4/6 Jens Seidel <jensseidel@users.sf.net>: > > > > Calling apt-get update on my OpenMoko phone (armel, 128MB RAM, sd card) > > > > takes forever: > > I found the problem. It was not swap specific and the update took only a > long time if called from inside a chroot from the SHR distribution. The > problem was the mount option "sync" which was used by the udev automounter > from /etc/udev/scripts/mount.sh. > > Is there anything the apt developers can improve? I'm not sure. Maybe a > optimization for this case would be good (reducing disk access) or checking > the mount options and outputting a warning? That seems silly, nobody else emits a warning. Mounting with sync is just wrong. Just closing the bug seems like the right course of action, so I do that hereby. > At least the bogus download rate I mentioned earlier should be fixed until > this bug gets closed. I think we had quite some rework in that area, it's still not optimal everywhere, but we can't get things optimal. -- Debian Developer - deb.li/jak | jak-linux.org - free software dev When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
--- End Message ---