VSTS Pioneer TFS2010 Dogfood Server: Statistics August 2009

(This blog post is part of a series of posts on the new VSTS Pioneer TFS dogfood server.)

Everybody loves statistics, so here are the statistics for the first month on the VSTS Pioneer server.

  • Recent Users: 415

Work Item Tracking

  • Users with Assigned Work Items: 2,454

  • Work Items: 111,319

  • Areas & Iterations: 2,811

  • Work Item Versions: 1,056,416

  • Work Item Attachments: 50,833

  • Work Item Queries: 2,965

Version Control

  • Files & Folders: 8,561,565

  • Compressed File Sizes (MB): 325,080

  • Uncompressed File Sizes (MB): 856,859

  • Checkins: 18,867

  • Shelvesets: 1,982

  • Merge History: 1,789,333

  • Pending Changes: 48,155

  • Workspaces: 727

  • Local Copies: 184,231,208

These statistics are captured by using the TFS Best Practices Analyzer and a custom configuration file. The configuration tells the BPA tool to run a series of SQL queries and dump the results to an XML file. I have then created an XSLT that transforms the results into a more user-friendly HTML file. The BPA tool is then scheduled to run every night and generate a fresh set of statistics. I’m working with the TFS BPA team to get this configuration built into the next version of the BPA tool – I don’t have an ETA on when that will ship, but stay tuned.

This month I’ve also pulled the last 30 days of PerfMon counters to see how our hardware choices are holding up. If you’d like to setup something like this for yourself, have a look at my previous posts.

Disk Performance

Things are looking OK on the IO front. 95% of the time we’re pushing 45MB/sec (Read) and 33MB/sec (Write) or less to and from our storage. The response time is <40ms which is nothing to worry about for the configuration we have.


50th Percentile

95th Percentile

99th Percentile

Avg. Disk sec/Read




Avg. Disk sec/Write




Disk Read Bytes/sec




Disk Write Bytes/sec




Avg. Disk Bytes/Transfer





The memory usage on our SQL server has remained completely constant. This is because SQL is set to use a fixed amount and Analysis Services & Reporting Services share the rest.

CPU Performance

(Avg: 32%). The majority of this usage is SQL Server, with a small portion going to Analysis Services & Reporting Services. It’s nice to see that we still have plenty of capacity left for the usage to grow.


That’s all for statistics, stay tuned for more next month.

Skip to main content