![\"image\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_2.png\")
<\/a> <\/p>\nIf you follow my dogfood statistics, you’ll notice that some of the numbers at the bottom are up quite a bit. The +200 recent user bump represents the increase in usage as we approach the completion of the roll out of TFS to the entire division. At this point I’m expecting the roll out to be done within 4 – 6 weeks. There’s been a corresponding increase in Local copies. We’ve also seen significant jumps in merge history as we do more and more of our large tree merges in TFS. The biggest jump is in downloads (almost 2X). This is due to the build lab ramping up. Yesterday, they rolled out config changes to download all files from a TFS Proxy and we should see that number fall substantially in next month’s report.<\/p>\n
We continue to refine the perf and scale of TFS. I think not a week goes by these days when we don’t push some update (or several) onto the production server to address our latest perf and scale issues. Most of the time it runs quite well but every so often just the right combination of huge (~million file) operations hit a problem and cause the overall server responsiveness to suffer. We’re making good progress but it’s no consolation when you are staring at the screen waiting for your one file to checkin just because someone else is checking in 400,000 deletes or some such. All of the fixes we make continue to flow into our TFS 2008 SP1 work so you should be able to get them later this year.<\/p>\n
Unlike TFS 2005 SP1 and TFS 2008 RTM, I don’t think the average user out there will see significant improvements from the additional performance work we’re doing in TFS 2008 SP1. Perhaps some small improvements but, at this point, most of the fixes we make are primarily address contention and\/or I\/O issues in really large scale operations. I know some of our customers do this but the majority do not.<\/p>\n
Here’s the statistics for this month…<\/p>\n