History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RHQ-417
Type: Sub-task Sub-task
Status: Accepted Accepted
Priority: Major Major
Assignee: Joseph Marques
Reporter: Joseph Marques
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project
RHQ-449

add optimizations for group plugin configuration updates

Created: 02/May/08 04:08 AM   Updated: 20/Jul/08 03:43 PM
Component/s: FX - Inventory, Core Server
Affects Version/s: 0.1
Fix Version/s: 2.0

Time Tracking:
Not Specified

Issue Links:
Relation
 


 Description  « Hide
as it stands today, group plugin configuration updates have been tested and work against resource groups as large as 20K resources, but the time it takes for such an update to complete is rather long. we're talking on the order of 50 updates / minute right now. pretty much, it comes down to the fact that each individual plugin update makes a separate request to the agent, and afterwards sits around and waits for a new service discovery to complete.

there is definitively room for improvement here. we could re-order the group update so as to batch the updates to each agent, and perform a single request for service discovery after all of the resources on any one agent complete. this could easily make the end-to-end time 10, 20, or even 30 times faster. the speed-up would be determined by the number of plugin configurations being updated on each agent; the more updates per agent, the greater the speed-up (for that sub-part of the end-to-end flow).

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Joseph Marques - 19/May/08 11:17 AM
actually, i think the best way to achieve this is to simply support executing runtime discoveries from a particular root resource as opposed to the entire hierarchy. this way, the server-side could blindly submit runtime discovery requests to an agent for multiple resources on a single agent without worrying that work will be duplicated.

Joseph Marques - 02/Jul/08 05:48 AM
this is a performance-related issue, so pushing to 2.0