[
https://issues.apache.org/jira/browse/CLOUDSTACK-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742847#comment-13742847
]
Sowmya Krishnan commented on CLOUDSTACK-4350:
---------------------------------------------
Already tried to generate trace logs for 18k-20K hosts with the DB dump that i
had. But i got blocked again due to issue: CLOUDSTACK-4371.
Due to this, i am not able to use DB dump to restore old data, but need to
again add hosts which takes about 7 hours. Will let this run and update the
logs when i have it.
Further to comment though, 3 sec is also pretty high for simulator host
considering we are adding 20K hosts. Earlier this used to take about 2 hours. 3
sec for one host is obviously high comparatively.
> [Performance Testing] Adding hosts take much longer time than baselines
> -----------------------------------------------------------------------
>
> Key: CLOUDSTACK-4350
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4350
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: 4.2, performance test env, with simulator
> Reporter: Sowmya Krishnan
> Assignee: Koushik Das
> Priority: Critical
> Labels: perfomance
> Fix For: 4.2.0
>
>
> Performance test setup:
> Basic zone, 1 host/cluster, tyring to deploy 20K simulator Hosts, with host
> tags
> Compared to baseline numbers, deploying hosts is taking much longer in the
> simulator environment
> For the 1st 1000 hosts, it took about 4 mins to deploy as per baseline
> With 4.2, the 1st 1000 hosts are taking almost 7 minutes
> Configurations:
> heap size: -Xmx12288m
> db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&prepStmtCacheSqlLimit=4096&includeInnodbStatusInDeadlockExceptions=true&logSlowQueries=true
> For 20K Hosts, the number exponentially increases and the deployment time
> also increases.
> Attaching trace logs of 4.2 for 1k simulator hosts deployment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
