New vCenter Operation Limits in VMware View 5.1

The Concurrent Operations Limits for vCenter Server and View Composer have changed. VMware vCenter and View Composer Advanced Settings allow administrators to specify the maximum concurrent number of provisioning, power and maintenance operations.  In View 5.0 only power and provisioning concurrent operations were available for configuration via the user Interface.

VMware View 5.1 not only implement management of maintenance and Linked-Clone provisioning operations but also increase the Default limits.

 

NEW (View 5.1)

image

OLD (View 5.0)

 

Max concurrent vCenter provisioning operations – Determines the maximum number of concurrent requests that View Manager can make to provision and delete full virtual machines in this vCenter Server instance.

Max concurrent power operations – Determines the maximum number of concurrent power
operations (startup, shutdown, suspend, and so on) that can take place on virtual machines managed by View Manager in this vCenter Server instance.

Max concurrent View Composer maintenance operations – Determines the maximum number of concurrent View Composer refresh, recompose, and rebalance operations that can take place on linked clones managed by this View Composer instance.

Max concurrent View Composer provisioning operations – Determines the maximum number of concurrent creation and deletion operations that can take place on linked clones managed by this View Composer instance.

 

The Default operation limits are recommended for most VMware View implementations. However, if you have a temporal workload in your environment you may want to have the ability to execute a large number of simultaneous operations; like when employees get to their workstations in the morning, or when students finish or start a class.

Changing the Default values may impact on vCenter and VMware View performance creating a performance bottlenecks on CPU, Memory or Storage. Be careful when changing those limits, always making sure you increase them by slow amounts while ensuring the infrastructure is handling well the new workload.

For more information refer to the VMware View 5.1 Administration Guide

 

This article was first published by Andre Leibovici (@andreleibovici) at myvirtualcloud.net.

 

4 comments

Skip to comment form

    • itzik on 08/23/2012 at 5:33 pm

    Andre,
    is there a maximum value for these records?

  1. @itzik

    The concurrent operation limits on View apply to a particular VC, and View will not override VC limits.

    For example, for View, the default concurrent provisioning operations for Linked clone is 8. So at any given time View would not trigger more than 8 provisioning operations concurrently, in that case, the concurrent provisioning operations on a single hosts/network/datastore would not exceed 8. Adjusting the host configuration to allow more than 8 without adjusting the View concurrent operation limits should take no effects.

    The effective concurrency per “resource” in a View deployment also depends on several other factors: number of clusters, number of hosts/network/datatore per resource pool. For example, for a given VC and a given View provisioning concurrent limit, the more hosts you have in a cluster, you less effective concurrency you will get on a per host level.

    So the answer here is, it depends on the maximum concurrent operations allowed on each host.

    Andre

  2. Max operations per ESXi host is 8, this is not configurable IIRC. So, my thinking is if you have 8 hosts in a cluster the theoretical max would be 64 view composer operations. Would this be right, Andre?

  3. Rick,

    The maximums are ver vCenter or View Composer instance. If you have 2 vCenter, each with it’s own View Composer, than you would have 2 x 8 = 16.

    Andre

Leave a Reply