Home > Blogs > VMware VROOM! Blog

vCenter Server 5.1 Database Performance with Large Inventories


Better performance, lower latency, and streamlined statistics are just some of the new features you can expect to find in the vCenter Server in version 5.1. The VMware performance team has published a paper about vCenter Server 5.1 database performance in large environments. The paper shows that statistics collection creates the biggest performance impact on the vCenter Server database. In vSphere 5.1, several aspects of statistics collection have been changed to improve the overall performance of the database. There were three sources of I/O to the statistics tables in vCenter Server—inserting statistics, rolling up statistics between different intervals, and deleting statistics when they expire. These activities have been improved by changing the way the relevant data is persisted to the tables, by partitioning the tables instead of using staging tables. In addition, by removing the staging tables, statistics collection is more robust, resolving the issues described in KB 2011523 and KB 1003878. Scalability is also improved by allowing larger inventories to be supported because they don’t take so long to read/write data from the old staging tables. The paper also includes best practices to take advantage of these changes in environments where vCenter Server has a large inventory. For more details, see vCenter Server 5.1 Database Performance in Large-Scale Environments.

Here are the URLs for the paper, “VMware vCenter Server 5.1 Database Performance Improvements and Best Practices for Large-Scale Environments”:




2 thoughts on “vCenter Server 5.1 Database Performance with Large Inventories

  1. Jannie Hanekom

    Nice whitepaper, but as something that purports to illustrate Performance Improvements in 5.1, I find it a bit wanting in terms of actual illustration.

    Timed figures for certain tasks are useful in re-affirming that higher statistics levels take longer to process than lower levels, but doesn’t do much more than that if we have nothing to compare it to. I’m sure that a Level 2 “Past Day” rollup of 01:20 on a database of 1,000 hosts and 10,000 VMs on the documented VC/SQL setup is fast, but we don’t know whether the VC 5.0 time was 01:21, or 01:01:20.

    It’s a shame, as it’s clear from the acknowledgements section that a lot of effort has gone into doing the actual testing and everyone was quite impressed with the improvements.

  2. Muktesh

    Performance is very important with any application.If your database tables have millions of records then a simple SQL query will take 3-4 mins.but ideal time for a query should be at max 5 sec. Now the Question comes “How can improve performance with large databases.“
    See this article http://techathon.mytechlabs.com/performance-tuning-while-working-with-large-database/


Leave a Reply

Your email address will not be published. Required fields are marked *