git-zlb.vips.scl3.mozilla.com is slow

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
2 years ago

People

(Reporter: jrmuizel, Unassigned)

Tracking

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1288] )

(Reporter)

Description

4 years ago
When cloning from this server I get only about 3MiB/s compared to the 5MiB/s I get from github.com

This ends up being the bottleneck when cloning a new b2g repo
Component: WebOps: Source Control → Git
Product: Infrastructure & Operations → Developer Services

Updated

4 years ago
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/226]

Updated

4 years ago
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/226] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1277] [kanban:engops:https://kanbanize.com/ctrl_board/6/226]

Updated

4 years ago
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1277] [kanban:engops:https://kanbanize.com/ctrl_board/6/226] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1282] [kanban:engops:https://kanbanize.com/ctrl_board/6/226]

Updated

4 years ago
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1282] [kanban:engops:https://kanbanize.com/ctrl_board/6/226] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1283] [kanban:engops:https://kanbanize.com/ctrl_board/6/226]

Updated

4 years ago
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1283] [kanban:engops:https://kanbanize.com/ctrl_board/6/226] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1288] [kanban:engops:https://kanbanize.com/ctrl_board/6/226]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1288] [kanban:engops:https://kanbanize.com/ctrl_board/6/226] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1288]

Updated

3 years ago
Assignee: server-ops-webops → nobody
QA Contact: nmaul
service decommissioned in bug 1277297
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.