[
https://issues.apache.org/jira/browse/CLOUDSTACK-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742185#comment-13742185
]
Koushik Das commented on CLOUDSTACK-4350:
-----------------------------------------
The response generation logic has changed, now it depends on a single view
(host_view) to generate the response instead of going to multiple database
tables like before. So that part should indeed be faster but the test results
show deterioration.
Need the following as well to proceed further:
- TRACE enabled logs for adding hosts, after 18-20K hosts have already been
added, to see where the delay is coming from as the normal logs suggests that
the max. time for agents to come 'Up' is ~3secs which indicates that response
generation might be taking time even with views.
- Based on the logs, add hosts related tests is done using port 8096. Would
need the logs based on port 8080 for add host. This would help in understanding
if there is any additional time getting spent before the actual AddHostCmd
starts executing and also if passing back the response is taking more time. I
can see a fix made for CLOUDSTACK-3274 that also has the possibility of
affecting the performance as the request/response is getting cleaned up of
sensitive data.
> [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
