New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 716199 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 714828



Sign in to add a comment

Stop sending name/non_unique_name

Project Member Reported by s...@chromium.org, Apr 27 2017

Issue description

We've historically been writing both of these fields with a fairly long string that requires model type logic to generate. However, we send it over the wire, and it is costing clients non-zero amounts of bandwidth and memory. This is fairly wasteful. While useful for sync-internals, we should strip it off before it gets to the wire for all types.

It is unclear to me how we can best balance getting it to sync-internals while also keeping it in memory for as little time as possible on normal commits.

Note that this is blocked by  issue 714828  which is converting name from required to optional.
 

Comment 1 by s...@chromium.org, Jan 17 2018

Status: Archived (was: Assigned)
This does not need to be done. Memory/bandwidth benefits have to be weighed against having less information to debug problems. Closing this for now as we have no current plans to do this in the short term.

Sign in to add a comment