[CONTROLLER-1448] Optimize NormalizedNode streaming by using a shared dictionary Created: 12/Nov/15 Updated: 05/Oct/18 Resolved: 05/Oct/18 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | Lithium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Moiz Raja | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||
| External issue ID: | 4626 | ||||||||||||
| Description |
|
When a NormalizedNode is streamed either for Persistence/Replication we encode it such that each streamed NormalizedNode contains a String Dictionary which is unique to a specific instantiation of a NormalizedNodeOutputStreamWriter. Since a shard essentially replicates and stores data for a specific subset of the total yang schema it is not optimal to have this per-instance dictionary persisted and replicated. Using a shared dictionary when streaming a NormalizedNode can significantly reduced the storage and network bandwidth requirements for streaming a NormalizedNode. |
| Comments |
| Comment by Robert Varga [ 08/Dec/15 ] |
|
The patch series consists of: |