Page History

...

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

Java version

java version "1.6.0"

...

Due to following issues, the runs haven't been completed

https://issues.apache.org/jira/browse/CLOUDSTACK-4371

https://issues.apache.org/jira/browse/CLOUDSTACK-4371https://issues.apache.org/jira/browse/CLOUDSTACK-4350

https://issues.apache.org/jira/browse/CLOUDSTACK-4350https://issues.apache.org/jira/browse/CLOUDSTACK-2918

https://issues.apache.org/jira/browse/CLOUDSTACK-2918https://issues.apache.org/jira/browse/CLOUDSTACK-3441

Tests on Advanced zone

...

1. CPU and Memory Utilization during deploy VM
2. Time for Async Job to complete
3. Time to return job id
4. DB connections

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

CPU Utilization measured in the Management server during deployment of 12K simulator VMs and post deploy when there were no external APIs being fired

LIST API RESPONSE TIME

Configuration:

...