Page History

PERFORMANCE TESTING RESULTS BEFORE API OPTIMIZATION

CONFIGURATIONS

1.      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

Java version

java version "1.6.0"

OpenJDK  Runtime Environment (build 1.6.0-b09)

OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode)

2.      Database

 Processor

Quad-Core AMD Opteron(tm) Processor, 2.1GHz, ht enabled, 8 processor

Operating System

CentOS release 6.2 (Final), x86_64

Configuration Parameters

DB configurations for this run is detailed in the my.cnf attached: my.cnf.txt

Mysql version

MySQL-server-5.5.21-1.linux2.6.x86_64

TEST ENVIRONMENT SET UP

Test Set up for this run consists of 1 zone with 1800 simulated hosts across over a hundred pods. 4000 accounts were created with each account having one network.

Following is the detailed configuration of the infrastructure:

1 Zone

Wiki Markup115 Pods \ [Each Pod having 2 Clusters\]

Wiki Markup230 Clusters \ [Each cluster having 8 hosts and one primary storage\]

1840 Hosts

Wiki Markup4000 User accounts \ [Each account having one network\]

12000 User instancesunmigrated-wiki-markup

8000 Virtual Routers \ [Since we are using Redundant Virtual Router offering\]

Performance Numbers for List APIs

...