Bringing you news, technical articles, and other useful content about Visual Studio ALM and Team Foundation Server
More videos »
The following analysis includes the IT internal offering for TFS and includes trends throughout the first half of 2012 (January – June 2012). Overall, we are continuing to see consistent growth. You can see the data from the second half of 2011 here.
The decrease in team projects between January and June is due to Team Project cleanup. Team Project cleanup in January also accounts for some of the trend data going down between January and February.
Service Offering
January 2012
June 2012
Growth
Instances
51
52
2%
Unique Users
34,067*
42,687
25%
Team Project Collections
273
313
15%
Team Projects
10,581
10,101
-5%
Work Items
13,837,104
15,502,244
12%
Source Code Files
148,689,374
191,608,280
29%
Builds Per Month
1,240,467
1,898,617
53%
Test Cases
2,583,880
3,023,416
17%
* Unique Users are from February 2012 instead of January 2012 due to miscalculation in January's report
The charts below show the top 10 IT-supported instances in several categories
“Unique Users” are the number of users that have accessed the instance in the month. This includes any TFS operation such as reading reports with data from TFS, using TFS Web Access to view or edit work items, or viewing or checking in source code. The sum of the unique users of each instance is greater than this number because some users access more than one instance.
This demonstrates the growth throughoutthe first half of 2012 for the full internal offering.
The data below is for each IT-supported TFS instance in June 2012
TPCs
Projects
Source Files
Builds Month
Total Builds
1
2,138
39
582,960
5,713,240
22,171
462,142
161,944
2
3,188
4
276,041
118,747
0
21
17,361
3
1,109
50
263,678
5,643,882
5,889
380,957
28,733
2,456
15
3,446
84,948
3,609,710
1,562
30,701
2,644
5
970
12
355
680,477
9,147,270
1,342
92,239
136,310
6
796
16
306
306,563
4,165,154
11,465
96,202
16,523
7
1,118
300
336,992
4,871,870
1,480
267,266
83,054
8
1,680
231
569,420
8,983,221
6,472
317,231
145,091
9
2,351
20
577
536,709
5,010,201
3,048
70,487
44,806
10
104
5,926
15,865
330
2,211
4,610
11
523
117
206,746
321,045
505
28,097
56,096
2,434
267
485,447
2,388,768
2,262
4,182,096
202,500
13
160
56
9,192
1,042,943
441
2,844
616
14
3,536
99
1,530,415
37,730,043
34,035
306,969
810
697
211
494,202
1,170,946
5,149
83,756
257,781
119
15,300
270,353
66
17,713
4,654
17
37
52,067
533,789
2,132
34,155
20,840
18
1,413
30
426
363,131
6,920,320
2,426
25,753
34,223
19
1,327
760
392,042
6,024,574
3,425
30,550
50,562
602
108,320
660,239
2,550
11,135
22,960
24
46
191
140
22
314
47,827
764,219
3,712
19,295
1,086
23
219
2,962
1,804,277
49
632
178
134
106
876,884
1,524,133
25
484
26
136
41,035
103,013
7,770
143
47,896
187,172
1,065
7,839
5,798
27
252
31
52,707
721,755
238
5,882
11,603
28
1,783
1,370
29
151
53
28,630
283,548
389
3,798
6,824
409
131,840
859,986
1,651,390
23,527,650
65,653
2,576
36
604,237
4,118,377
90,923
1,140,498
199,692
32
224
218,408
5,348,772
33
96
43
42,387
648,348
1,483
261,248
9,831
34
6,974
28,202
2,396
35
1,035
124,393
45,708
7,195
427
332
245,658
3,286,706
491
92,211
25,718
795
148,165
671
70
38
486
120
358,771
6,859,503
837
79,401
124,071
128
61
22,714
832,652
89
6,187
946
40
2,777
371
1,357,828
12,806,844
17,106
1,025,757
493,184
41
2,526
440
1,037,684
10,632,670
4,253
381,021
340,354
42
1,050
209
385,968
24,318,313
3,654
399,101
108,907
1,476
336
681,684
7,587,388
10,769
726,245
93,379
44
75
1,297
162,607
110
2,657
45
365
301,758
492,886
686
947,528
209,520
36,066
7,809
47
48
2,334
22,513
181
2,551
901,572
2,745,481
1,701
22,679
8,497
223
19,816
815,346
2,173
78,667
1,307
792
58,070
239,348
737
18,425
4,345
1,168
414,128
17,703
3,885
It would be interesting to know what % of builds were done using the tfs preview build service.
These numbers are for the IT-run internal TFS instances (physical TFS servers, not TFS Preview accounts), so all of the builds included here are using on-premises build agents.
Thanks,
Erin
Nice stats :)
Cool stats. Way bigger than our TFS environment. Do you guys also have database sizes and average build times by chance ?
Hi Rolf,
The largest instance, DevDiv, uses 13TB of storage. About 10 instances have team project collections of over a TB. This is good feedback, I'll include some more detailed storage numbers in the next set of stats.
preview of build service is good
<a href="http://aworkzone.com">Aworkzone</a>
Which row is DevDiv? Also the numbers seem misleading as a Team Project is a really large container for DevDiv and a Team Project is a really small container for MSN. It would be great if you broke out the states by individual team project.
I think row 14 is DevDiv....so why does devdiv have 99 projects? I had heard that all of DevDiv was under 1 team project.....why did DevDiv structure their team projects this way?
Hi Erin - thanks for sharing! What would also be interesting and valuable would be some performance #'s/averages over time that show how the environment(s) are handling all that volume and indicate the client user experience. Would love to see that for DevDiv if you have it.
@Mike and Neil,
Yes, row 14 is DevDiv. You're completely correct that different teams use Team Projects and Team Projects Collections quite differently. For DevDiv, we have one huge team project for VS2012 and one huge team project on a different collection for VS2010. There are 99 individual team projects because this contains the projects in all of our Team Project Collections. This includes projects from all the way back to VS2005 and many one-off projects, servicing projects, individual incubation projects, etc. But the majority of the data is in the two main team projects, the VS2012 and VS2010 projects.
There are other teams that use hundreds of small team projects that have a definitive lifetime of only a few months. This is why there is such a range on different instances.
@Ryan,
Thanks for the feedback about performance. We do have this data, but mostly from the server side (i.e. how long each command takes to execute once the server receives it). I'll look into what information is available and what we can share.
Hi Erin
it is possible to provide the queries to generate these reports