Churn on VMWResourcePool (4292556)

The following Churn can be observed from Diagnostic Snapshot:

---------- Begin Frequent Changes for Type VMWResourcePool ----------

Most volatile object: Test - New VMs Here (VMWResourcePool)
Object uniqueId: 6d6c1654-c903-43e1-b9ea-f69949ca3aa1
Current version: 13907
Number of object updates in period: 1951
Number of versions in period: 281
Number of recent changes: 166
Num changes by property:
    cpuAllocationLimit: 63
    memoryAllocationLimit: 100
    virtualMachines: 3

Details of recent changes:
+-------------------------+-----------------------+---------------+---------------+---------------+
| Timestamp               | Property              | Change Type   | Old Value     | New Value     |
+-------------------------+-----------------------+---------------+---------------+---------------+
| 2016-12-09 23:09:12.803 | memoryAllocationLimit | Value Change  | 10620020      | 10619994      |
| 2016-12-09 23:04:14.459 | cpuAllocationLimit    | Value Change  | 1435324000000 | 1436134000000 |
| 2016-12-09 23:04:14.459 | memoryAllocationLimit | Value Change  | 10620072      | 10620020      |
| 2016-12-09 22:59:02.865 | cpuAllocationLimit    | Value Change  | 1434514000000 | 1435324000000 |

Alternative Workaround: 

1). Please run attached file "find-frequent-changes_VMWResourcePool_object.groovy" from Administration │ Tooling │ Script Console │ Script,           and click on "Add" button.

2). Add to Object "VMware Resource Pool" to server.topology.objectExpiryDays, please KB SOL206989 in order to do it and set Stale Object clean       up time.

3). Then go to Administration │Management Server │ Servers │ Object Clean up. Then check for Topology objects size for "VMware Resource  Pool" and keep monitoring, Daily Maintenance will remove stale objects.