Re: F13 install timings
On 03/19/2010 03:41 PM, John Reiser wrote: It's an http install to a local server, and there is no access during that stage (after is has all of the repodata files) until it starts fetching package headers. So, it seems like filing a bug is in order. Anaconda or yum? Anaconda, the program that you invoked. If anaconda can pass the blame along to yum, then I'm sure that they will :-) https://bugzilla.redhat.com/show_bug.cgi?id=575878 -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F13 install timings
OP == Orion Poplawski or...@cora.nwra.com writes: OP The install spends a long time displaying Checking dependencies in OP packages selected for installation with no movement of the progress OP bar. My kickstart installs used to sit showing that for ages; I ended up using pungi -G to gather an install set of just what I have in the kickstart file. This seems to make things run much, much faster, although I've never worked on figuring out why. - J -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F13 install timings
I don't know if it is too early to do install timings (due to debugging be on in the kernel, elsewhere?) but here are the longest steps from a fairly stripped down kickstart server install of about 389 packages: F-13: enablefilesystems 3:10s postselection24:27s installpackages 14:30s F-12: enablefilesystems 2:50s postselection36:45s installpackages 11:36s (probably had more packages in our local cache) The install spends a long time displaying Checking dependencies in packages selected for installation with no movement of the progress bar. Any way this could get sped up more (good job going from 36m to 24m) and progress shown? Interestingly a much larger install set on a laptop took only 1:34s in postselection. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F13 install timings
... stripped down kickstart server install of about 389 packages: enablefilesystems 3:10s postselection24:27s installpackages 14:30s The install spends a long time displaying Checking dependencies in packages selected for installation with no movement of the progress bar. Interestingly a much larger install set on a laptop took only 1:34s in postselection. Are you sure that the optical drive on the server is OK? Those times for postselection (tens of minutes) smell like slow hardware [microcode] recovery for seek errors. Transfer the DVD to a USB2.0 flash memory device, boot the netinstall CD with extra parameter 'askmethod', choose local harddrive, and select the flash memory partition as the source of the Fedora 13 tree. Postselection should take less than one minute. -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F13 install timings
On 03/19/2010 01:57 PM, John Reiser wrote: ... stripped down kickstart server install of about 389 packages: enablefilesystems 3:10s postselection24:27s installpackages 14:30s The install spends a long time displaying Checking dependencies in packages selected for installation with no movement of the progress bar. Interestingly a much larger install set on a laptop took only 1:34s in postselection. Are you sure that the optical drive on the server is OK? Those times for postselection (tens of minutes) smell like slow hardware [microcode] recovery for seek errors. Transfer the DVD to a USB2.0 flash memory device, boot the netinstall CD with extra parameter 'askmethod', choose local harddrive, and select the flash memory partition as the source of the Fedora 13 tree. Postselection should take less than one minute. It's an http install to a local server, and there is no access during that stage (after is has all of the repodata files) until it starts fetching package headers. So, it seems like filing a bug is in order. Anaconda or yum? -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
