Bug 106222 - very slow instlattion when doing an "upgrade" install
Summary: very slow instlattion when doing an "upgrade" install
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: i586 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-22 16:08 UTC by Simon Crute
Modified: 2005-08-23 12:38 UTC (History)
1 user (show)

See Also:
Found By: IS&T
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast2 install logs (349.33 KB, application/x-bzip2)
2005-08-22 16:12 UTC, Simon Crute 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Crute 2005-08-22 16:08:21 UTC 
I was doing an "upgrade" install of 10.0b2 from 9.3. 
I was installing over the network from an install point on the same 100Mbps
network as I am on. No significant other network trafic. 

The install took over 3 hours from starting to copy files until it was finished. 
yast2 logs attached.
Comment 1 Simon Crute 2005-08-22 16:12:38 UTC 
Created attachment 46991 [details]
yast2 install logs

A tar.bz2 of the yast2 log files from the installation.
Comment 2 Arvin Schnell 2005-08-22 19:56:32 UTC 
Seems as the backup option was turned on.  Don't know if that's the
default.  Otherwise I guess it's simply that slow with more than 2000
packages installed.
Comment 3 Jiri Srain 2005-08-23 12:21:48 UTC 
Arvin, what did you mean with the "backup option"?  
 
The biggest time consumer (according to log) is RPM itself. Sorry, but there 
is nothing we could do about it. Therefore WONTFIX (#define WONTFIX CANTFIX)
Comment 4 Arvin Schnell 2005-08-23 12:32:09 UTC 
With "backup option" I mean the check for modified files belonging
to any RPM.  In the proposal its the checkbox Create Backup of
Modified Files" under the title "Backup". And it's on per default.
Comment 5 Klaus Kämpf 2005-08-23 12:38:30 UTC 
This is really RPMs fault. RPM is kind of stupid when it comes to database 
operations. It always reads the complete rpmdb into memory, changes it, and 
writes it back out. 
Instead of calling the rpm binary, one could also link to librpm and use its 
functions. We tried this already and lots of other bugs appeared :-(