Red Hat Bugzilla – Bug 912871
Perf: resource configuration update taking a lot of backend resources
Last modified: 2013-09-03 10:42:09 EDT
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.
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.
related to this area, I added a concurrency limit to the config update API which helped alot. See bug #912525
Setting to ON_QA, although these changes are implicit and handled by
integration testing. Recommend to close.
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.