[IGNITE-5097] BinaryMarshaller should write ints in "varint" encoding where it makes sense

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0
• Fix Version/s: 3.0
• Component/s: binary
• Labels: iep-2 performance
• Assignee: Vyacheslav Daradur
• Reporter: Vladimir Ozerov
• Created: 27/Apr/17 08:08
• Updated: 20/Dec/19 10:43

Description

There are a lot of places in the code where we write integers for some special purposes. Quite often their value will be vary small, so that applying "varint" format could save a lot of space at the cost of very low additional CPU overhead.

Specifically:
1) Array/collection/map lengths
2) BigDecimal's (usually will save ~6 bytes)
3) Strings
4) Enum ordinals

Issue Links

• Blocked: IGNITE-6418 Binary: optionally write integer datatypes with varint encoding
• links to: GitHub Pull Request #2821
• links to: TeamCity PR tests
• links to: Upsorce review #362

Sub-Tasks

• .NET: BinaryMarshaller should write ints in "varint" encoding where it makes sense: Resolved
• CPP: BinaryMarshaller should write ints in "varint" encoding where it makes sense: Resolved
• Java: BinaryMarshaller should write ints in "varint" encoding where it makes sense: Resolved
• Provide compatibility property to allow to keep data in old format: Resolved
• Add test of backward-compatibility: Resolved
• CPP: Implement 'varint' solution to be configurable via BinaryConfiguration: Open