On Mon, 2008-03-31 at 12:28 +0800, John Summerfield wrote: > seth vidal wrote: > > On Mon, 2008-03-31 at 11:44 +0800, John Summerfield wrote: > >> John Summerfield wrote: > >>> seth vidal wrote: > >> > >>> It's an HP dc7700, 2 Gbytes of RAM. > >> Probably should've mentioned "64-bit." > >> > > > > but you never mentioned what it was doing when it was 'glacially' slow. > > > > if you can recreate it run this command: > > > > echo 'n' | yum -d3 whateveryourcommandwas | grep 'time:' > > That would not measure what I mostly do. Everything up to that point is what yum does and where yum speed ups impact. After the confirmation all you have is: 1. package downloading - dependent on the speed/type of your network connection + mirrors 2. package gpg checking - happens while they download and is in rpm-land for all intents and purposes 3. transaction test - entirely in rpm-land. Yum can't do anything about it at all 4. transaction run - entirely in rpm-land - yum just reports what's going on. If your report of 'glacial' speed is AFTER the confirmation then your complaint is either with your ISP, your mirror or with rpm. Not with yum. -sv -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
