Steps to reproduce the problem?
(1) Login to existing sync profile by new client.
(2) Look for number of tombstone updates on chrome://sync-internals 

USS and directory types do not use tombstone updates on first association.
So we send unused data form server to client.
Initial get update could be very massive and tombstone update could reach 30%.
We can reduce time of initial association if filter tombstone updates on server.


 

Steps to reproduce the problem?
(1) Login to existing sync profile by new client.
(2) Look for number of tombstone updates on chrome://sync-internals 

USS and directory types do not use tombstone updates on first association.
So we send unused data from server to client.
Initial get update could be very massive and tombstone updates could reach 30%.
We can reduce time of initial association if filter tombstone updates on server.