On-Demand Services SDK for Tanzu 0.44

Data on Deployment Performance and Sizing for On-Demand Service Instances

Last Updated October 25, 2024

This topic shows you 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. The setup and results are shown here.

Set up

Environment
IaaSGoogle Cloud Platform
Tanzu Operations Managerv1.9.7
Elastic Runtimev1.9.13
Example Kafka On-Demand Tilev0.15.1
BOSH Director Configuration
Workers3
Dedicated status workerenabled
On-demand plan configuration
Zookeeper VM typesmall (1 CPU, 2GB RAM, 8GB Disk)
Kafka VM typesmall (1 CPU, 2GB RAM, 8GB Disk)

Test

  1. Upload the example Kafka on-demand tile.

  2. Configure the on-demand plan.

  3. Apply changes to install the on-demand service, ensuring that Register On-Demand Broker is checked.

  4. Create N dedicated service instances using the cf CLI.

  5. Make a change to the plan configuration.

  6. Apply pending changes, ensuring that Upgrade All On-Demand Service Instances is selected.

  7. Delete the tile and apply changes, ensuring that Delete All On-Demand Service Instances is selected.

Results

Durations presented in HH:MM:SS format.

Create50101500
average create00:01:0200:01:0300:01:02
total00:51:2801:45:4008:33:37
Upgrade All50101500
average upgarde00:01:1000:01:0500:01:00
total00:58:3701:49:4208:21:08
Delete All50101500
average delete00:05:0900:05:040:05:00
total04:17:3808:31:1041:38:26

These durations might 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

Notes

For create operations, the on-demand broker creates a BOSH deployment for each service instance. By default, the BOSH Director in Tanzu Operations 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, Tanzu Operations Manager runs a BOSH errand. This errand task occupies a BOSH Director worker, leaving one worker available to upgrade, or delete deployments.