Data on Deployment Performance and Sizing
This topic contains test data on on-demand service instances managed in a deployment.
VMware tested the on-demand broker (ODB) with 500 on-demand service instances using the example Kafka on-demand tile. We recorded how long it took to create, upgrade all, and delete all, with 50, 101, and 500 dedicated service instances. Setup and results are shown below.
|IaaS||Google Cloud Platform|
|Example Kafka On-Demand Tile||v0.15.1|
|BOSH Director Configuration|
|Dedicated status worker||enabled|
|On-demand plan configuration|
|Zookeeper VM type||small (1 CPU, 2GB RAM, 8GB Disk)|
|Kafka VM type||small (1 CPU, 2GB RAM, 8GB Disk)|
Upload the example Kafka on-demand tile.
Configure the on-demand plan.
Apply changes to install the on-demand service, ensuring that Register On-Demand Broker is checked.
Create N dedicated service instances using the cf CLI.
Make a change to the plan configuration.
Apply pending changes, ensuring that Upgrade All On-Demand Service Instances is checked.
Delete the tile and apply changes, ensuring that Delete All On-Demand Service Instances is checked.
Durations presented in HH:MM:SS format.
These durations may vary for a number of reasons, for example:
- Number of BOSH director workers
- IaaS performance
- Network latency
- Service instance BOSH release(s)
- Service instance deployment configuration
- VM type of service instance
- Activity of Elastic Runtime
- Activity of BOSH Director
For create operations, the on-demand broker creates a BOSH deployment for each service instance. By default, the BOSH Director in Ops Manager v1.9 has three workers with a dedicated status worker, so only two workers are available to process deployment tasks. Therefore, only two service instances can be created at the same time.
For upgrade all and delete all operations, Ops Manager runs a BOSH errand. This errand task occupies a BOSH Director worker, leaving one worker available to upgrade, or delete deployments.