
PERFORMANCE STUDY /7
VMware vCloud Director 1.0 Performance and Best Practices
Table 2. Oracle Database Configuration Parameters
ORACLE CONFIGURATION PARAMETER VALUE FOR C CELLS
CONNECTIONS 75 ×
C
+ 50
PROCESSES = CONNECTIONS
SESSIONS = PROCESSES × 1.1 + 5
TRANSACTIONS = SESSIONS × 1.1
OPEN_CURSORS = SESSIONS
A database administrator can set these values in Oracle.
For more information on best practices for the database, refer to the
vCloud Director Installation and
Configuration Guide
[10] .
Sizing for Number of Cell Instances
vCloud Director can be easily scaled up by adding more cells to the system. We tested with up to 12 cell instances
with 10 fully loaded vCenter Server instances.
For this experiment, the Oracle database instance ran in a host with 12 cores and 16GB RAM. Each cell ran in a
virtual machine with 2 vCPUs and 4GB RAM.
In general, we recommend:
number of cell instances = n + 1 where n is the number of vCenter Server instances
This formula takes into account the considerations for VC Listener (which helps keep the vCenter Server
inventory up-to-date in the vCloud Director database), cell failover, and cell maintenance. In “Inventory Sync” on
page 23, we recommend a one-to-one mapping between VC Listener and the vCloud cell. This ensures the
resource consumption for VC Listener is load balanced between cells. We also recommend having a spare cell for
cell failover. This keeps the load of VC Listener balanced when one vCloud Director cell fails or is powered down
for routine maintenance.
We assume here that the vCenter Server instances are managing a total of more than 2000 VMs. If the vCenter
Server instances are lightly loaded, multiple instances can be managed by a single vCloud Director cell. For cases
where vCenter Server is lightly loaded, use the following sizing formula:
number of cell instances = n ÷ 3000 + 1 where n is the number of expected powered on VMs
For more information on the configuration limits in vCenter Server 4.0 and 4.1, refer to
VMware vCenter Server
4.0 Configuration Limits
[4],
VMware vCenter Server 4.1 Configuration Limits
[5], and
VMware vCenter Server 4.1
Performance and Best Practice
[6].
Komentarze do niniejszej Instrukcji