Bug 912871

Summary:	Perf: resource configuration update taking a lot of backend resources
Product:	[Other] RHQ Project	Reporter:	Jay Shaughnessy <jshaughn>
Component:	Performance	Assignee:	Jay Shaughnessy <jshaughn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5	CC:	hrupp, mazz
Target Milestone:	---
Target Release:	RHQ 4.6
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-03 14:42:09 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:
Embargoed:

Description Jay Shaughnessy 2013-02-19 21:39:32 UTC

Agents discovering large inventories of resources with resource config can hammer the server, especially with the initial res config updates.

We need to look into concurrency limits and also general algorithms involved in the updates.

Comment 1 Jay Shaughnessy 2013-02-19 21:42:13 UTC

master commit 4385fbb69a2dfd9aced1f8802e9477dfb44860ae

Scalability work for resource config update.  We already added concurrency limits
that should throttle how many config updates the server gets hit with at one
time but we also want to see if we can relieve the intense banging on the db
and speed up the update time for each resource.

Comment 2 John Mazzitelli 2013-02-20 14:55:35 UTC

related to this area, I added a concurrency limit to the config update API which helped alot. See bug #912525

Comment 3 Jay Shaughnessy 2013-02-20 14:57:28 UTC

Setting to ON_QA, although these changes are implicit and handled by
integration testing.  Recommend to close.

Comment 4 Heiko W. Rupp 2013-09-03 14:42:09 UTC

Bulk closing of issues in old RHQ releases that are in production for a while now.

Please open a new issue when running into an issue.