Bug 787046

Summary:	Launching a deployment with large number of assemblies generates alot of requests to iwhd
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Richard Su <rwsu>
Component:	aeolus-conductor	Assignee:	Richard Su <rwsu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brad P. Crochet <brad>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	akarol, deltacloud-maint, ssachdev
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-30 17:17:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Richard Su 2012-02-03 02:00:12 UTC

Description of problem:
A deployment with 25 assemblies each using the same image generates ~ 2277 requests to iwhd.

The conductor/deployments/launch_time_params page takes about 14.4 seconds to load.

How reproducible:

always

Comment 1 Richard Su 2012-02-03 02:14:24 UTC

Most of these operations are duplicates and should be cached in some way. There has been some talk about storing the metadata in a database. If these operations are then converted into SQL queries in rails, they would then be cached automatically. This seems like the most sensible way to approach these types of problems.

Until then I've posted a patch that refactors the code to reduce the number of calls by reusing the objects retrieved from the warehouse. This reduces the number of operations to ~ 866 for 25 assemblies. Page load time is down to about 6.4 seconds.

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008607.html

Comment 2 Richard Su 2012-02-06 17:24:00 UTC

conductor commit e1441517424d8f755deca26f0e0367c704a65798

Comment 3 Richard Su 2012-02-07 17:05:03 UTC

Change is in aeolus-conductor-0.8.0-22

Comment 4 Shveta 2012-02-24 05:53:38 UTC

Launched a deployment with 25 assemblies of same image .. Much less iwhd requests 
are raised as seen in iwhd log and it took around 6 -7 seconds to load the page after launch

Verified in 

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch