[OAK-4471] More compact storage format for Documents

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: documentmk
• Labels: performance
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 15/Jun/16 05:23
• Updated: 07/Nov/17 13:23

Description

Aim of this task is to evaluate storage cost of current approach for various Documents in DocumentNodeStore. And then evaluate possible alternative to see if we can get a significant reduction in storage size.

Possible areas of improvement

1. NodeDocument
   1. Use binary encoding for property values - Currently property values are stored in JSON encoding i.e. arrays and single values are encoded in json along with there type
   2. Use binary encoding for Revision values - In a given document Revision instances are a major part of storage size. A binary encoding might provide more compact storage
2. Journal - The journal entries can be stored in compressed form

Any new approach should support working with existing setups i.e. provide gradual change in storage format.

Possible Benefits
More compact storage would help in following ways

1. Low memory footprint of Document in Mongo and RDB
2. Low memory footprint for in memory NodeDocument instances - For e.g. property values when stored in binary format would consume less memory
3. Reduction in IO over wire - That should reduce the latency in say distributed deployments where Oak has to talk to remote primary

Note that before doing any such change we must analyze the gains. Any change in encoding would make interpreting stored data harder and also represents significant change in stored data where we need to be careful to not introduce any bug!

Issue Links

• is related to: OAK-1312 Bundle nodes into a document