-
Notifications
You must be signed in to change notification settings - Fork 49
/
housekeeping-git-traffic.html
144 lines (141 loc) 路 3.06 KB
/
housekeeping-git-traffic.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
---
layout: default
title: Git Traffic
permalink: /housekeeping-git-traffic
---
<div class="chart-placeholder">
<h3>Operations</h3>
<canvas
data-url="{{ site.dataURL }}/git-download.tsv"
data-type="history"
data-config='{
"views":
[
{
"label": "2 m",
"tooltip": "Show the last 2 months",
"aggregate": false,
"series":
[
"clones",
"fetches"
],
"slice": [0, 61]
},
{
"label": "2 y",
"tooltip": "Show the last 2 years",
"aggregate":
{
"period": "week",
"method": "sum"
},
"series":
[
"clones",
"fetches"
],
"slice": [0, 106],
"default": true
},
{
"label": "all",
"tooltip": "Show all data",
"aggregate":
{
"period": "week",
"method": "sum"
},
"series":
[
"clones",
"fetches"
]
}
]
}'></canvas>
<div class="info-box">
<p>
<em>Cloning</em> a Git repository is expensive, as the entire repository history must be transferred.
Clients that have cloned a repository before should rather <em>fetch</em> the latest changes.
This is (sometimes dramatically!) faster for the client and less expensive for the server.
</p>
<p>
High numbers of clone operations usually indicate an unfavorably configured CI process.
</p>
<p>
Attention: These numbers are likely incorrect on a configuration with active replicas.
</p>
</div>
</div>
<div class="chart-placeholder">
<h3>Transferred Data</h3>
<canvas
data-url="{{ site.dataURL }}/git-download.tsv"
data-type="history"
data-config='{
"views":
[
{
"label": "2 m",
"tooltip": "Show the last 2 months",
"aggregate": false,
"series":
[
"clone traffic [GB]",
"fetch traffic [GB]",
"LFS traffic [GB]"
],
"slice": [0, 61]
},
{
"label": "2 y",
"tooltip": "Show the last 2 years",
"aggregate":
{
"period": "week",
"method": "sum"
},
"series":
[
"clone traffic [GB]",
"fetch traffic [GB]",
"LFS traffic [GB]"
],
"slice": [0, 106],
"default": true
},
{
"label": "all",
"tooltip": "Show all data",
"aggregate":
{
"period": "week",
"method": "sum"
},
"series":
[
"clone traffic [GB]",
"fetch traffic [GB]",
"LFS traffic [GB]"
]
}
]
}'></canvas>
<div class="info-box">
<p>
The amount of data transferred for clones and fetches (<em>excluding</em> Git LFS traffic) as well as pure <a href="https://git-lfs.github.com/">Git LFS</a> traffic (indirectly triggered through clones and fetches).
</p>
<p>
To save resources, you should try to minimize the number of clones, especially for large repositories.
</p>
</div>
</div>
<div class="chart-placeholder">
<table data-url="{{ site.dataURL }}/git-download-detailed.tsv" data-type="table"></table>
<div class="info-box">
<p>
This table lists the repositories that accounted for the majority of the traffic yesterday.
</p>
</div>
</div>