Bug 1302316

Summary:	rpm database access slow as hell
Product:	[Fedora] Fedora	Reporter:	customercare
Component:	rpm	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	22	CC:	ffesti, jzeleny, lkardos, novyjindrich, packaging-team-maint, pknirsch
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-19 08:29:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description customercare 2016-01-27 13:29:35 UTC

This seems to be a reinvention of this Bug:

https://bugzilla.redhat.com/show_bug.cgi?id=752897


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):

RPM-Version 4.12.0.1

How reproducible:    85%

Comment 1 customercare 2016-01-27 13:30:45 UTC

my fault, i just opened too much bugs for my fedora 23 desktop system ;)

Comment 2 customercare 2016-01-27 13:47:30 UTC

seem to be fixed with :  rpm -v --rebuilddb

Comment 3 Florian Festi 2016-02-19 08:29:33 UTC

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.