Page History

...

-        db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&prepStmtCacheSqlLimit=4096&includeInnodbStatusInDeadlockExceptions=true&logSlowQueries=true

The results along with the graphs can be seen in the following attached document:

Graphs_Advzone.docx

Test Scenario 5:

Restart Management Servers and track the time for host re balancing. Also track the numbers when few hosts are put into maintenance mode.

Following shows the time taken for each restart:

TC1: Stop both management servers. Then start up both. Time taken for all hosts to get to Up state: ~13 mins

TC2: Stop one management server. Time taken for hosts of that management server to get to Up state: ~5 mins

TC3: Start up the stopped management server. Time taken for hosts to rebalance between the 2 management server: ~16 mins

Now, add few hosts into maintenance mode and repeat the above restarts. Following are the time taken in each scenario:

TC1: ~10 mins

TC2:  ~5 mins

TC3:  ~13 minsCPU Utilization measured in the Management server during deployment of 12K simulator VMs and post deploy when there were no external APIs being fired Image Removed

LIST API RESPONSE TIME

...