PropertyCollector Performance

Various factors affect the performance of a PropertyCollector for any given session.

• Number of objects
• Number of properties
• Density of property data (composite, nested data objects)
• Frequency of changes to the objects and properties on the server
• Depth of traversal (number of properties traversed)

In addition, a vSphere server is affected by the number of PropertyCollector instances and the number of filters each instance is supporting across all sessions on the server.

To minimize PropertyCollector overhead and the amount of network traffic for your client application, use View objects with the PropertyCollector. Simple PropertyCollector Example (Java) illustrates using views with the PropertyCollector.