Page MenuHomePhabricator

Capacity planning for (& optimization of) transport backhaul vs edge egress
Open, MediumPublic

Description

[currently more of a placeholder than a task; sub-tasks to follow]

There exists all of:

  • a lack of a strong understanding of what the ratio between edge egress traffic and transport backhaul "should" be, under conditions ranging from warm-cache steady-state, to bringing up a 'cold' edge DC, to various attack scenarios
  • a lack of an intuitive awareness of & observability of as to what some of the backhaul traffic is, as was witnessed in T263206: cr1-codfw<->cr1-eqiad link saturation
  • several possibilities to optimize said ratio -- most past caching improvement efforts have focused specifically on per-request hitrate, and not on backhaul byte conservation.

Event Timeline

CDanis triaged this task as Medium priority.Sep 18 2020, 5:49 PM
CDanis created this task.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
ayounsi closed subtask Restricted Task as Resolved.Sep 24 2020, 11:15 AM
BBlack added a subscriber: BBlack.

The swap of Traffic for Traffic-Icebox in this ticket's set of tags was based on a bulk action for all tickets that aren't are neither part of our current planned work nor clearly a recent, higher-priority emergent issue. This is simply one step in a larger task cleanup effort. Further triage of these tickets (and especially, organizing future potential project ideas from them into a new medium) will occur afterwards! For more detail, have a look at the extended explanation on the main page of Traffic-Icebox . Thank you!