Bug 1302316 - rpm database access slow as hell
rpm database access slow as hell
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
i686 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-27 08:29 EST by customercare
Modified: 2016-02-19 03:29 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-19 03:29:33 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description customercare 2016-01-27 08:29:35 EST
This seems to be a reinvention of this Bug:


Description of problem:

Systeminfo: 4x XEON 1230v3  10 GB ram and SSD drives and next to no io at that moment : 

[root]# time rpm -qa >/dev/null 

real	1m20.141s
user	0m3.941s
sys	0m0.978s

We use a software to determin which version of the kernel and other services are installed, to give the server owner an information. This problem slows down this simple task, which takes seconds normally. 

We have 1061 packages installed. 

Interesstingly, it does not always take so long. From time to time, it behaves normally, but in the last days it was extrem anoying.

Version-Release number of selected component (if applicable):


How reproducible:    85%
Comment 1 customercare 2016-01-27 08:30:45 EST
my fault, i just opened too much bugs for my fedora 23 desktop system ;)
Comment 2 customercare 2016-01-27 08:47:30 EST
seem to be fixed with :  rpm -v --rebuilddb
Comment 3 Florian Festi 2016-02-19 03:29:33 EST
This is probably to some issues with bdb5. As we are going to move a way from bdb in the future and bdb5 is outdated we are not changing anything there.

Yes, rpm -v --rebuilddb recreates the db and should solve the problem by creating fresh structures that have not yet have been fragmented.

Note You need to log in before you can comment on or make changes to this bug.