[
https://issues.apache.org/jira/browse/CLOUDSTACK-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736745#comment-13736745
]
Koushik Das commented on CLOUDSTACK-4158:
-----------------------------------------
I looked at the listRouters, listEvents, listEvents and listAsyncJobs APIs and
in all cases I found that there is no change in the code between 4.1 and 4.2.
Also there is no change in the db views in most cases except for the addition
of a 1 or 2 new properties in the views.
Given this I don't think the numbers that we are getting as part of the perf.
runs is fully reliable unless we run the same tests on both 4.1 and 4.2 again
on the same environment. After running 4.1 and 4.2 on the same environment if
we still seeing any increase in time then the TRACE enabled logs from both runs
needs to be compared to see where is the increase in time coming from.
> [Performance Testing] List API performance in comparison to 4.1 is not as good
> ------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4158
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4158
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.2.0
> Environment: Simulator for creating mock resources, advanced zone, RVR
> Reporter: Sowmya Krishnan
> Assignee: Koushik Das
> Priority: Critical
> Fix For: 4.2.0
>
>
> Executed few List API calls for tracking performance runs for 4.2 and
> compared the results with 4.1. Most APIs are taking noticeably longer as
> compared to 4.1
> Examples:
> API Time taken in 4.1 Time taken in 4.2
>
> listAccounts 1m25.348s 2m22.628s
> listEvents 0m6.575s 0m20.277s
> Results so far are posted here (including comparitive results)
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Performance+Test+Execution+for+4.2
> Performance Test bed details:
> =======================
> Management server:
> Processor
> Dual core Intel(R) Xeon(R) CPU processor, 2.27GHz, ht enabled, 4 processor
> Operating System
> CentOS release 5.5 (Final), x86_64
> Configuration Parameters
> Following config parameters were used in both the management servers
> - Java heap size = 5 GB
> - db.cloud.maxActive = 250
> -
> db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&prepStmtCacheSqlLimit=4096&includeInnodbStatusInDeadlockExceptions=true&logSlowQueries=true
> Setup:
> =====
> Advanced zone, 2 Management Servers, 124 Pods [Each Pod having 2 Clusters]
> 248 Clusters [Each cluster having 8 hosts and one primary storage]
> 2000 Hosts
> 4000 User accounts [Each account having one network]
> 4000 User instances
> ~8000 Virtual Routers [Since we are using Redundant Virtual Router offering
> Didn't notice any slow queries logged in DB.
--
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
