[
https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030851#comment-16030851
]
ASF GitHub Bot commented on IGNITE-5097:
----------------------------------------
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/2043
IGNITE-5097: writing arrays length in varint encoding was implemented
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-5097_2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2043.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2043
----
commit 5af11ed85fe033ab2d4b70de7b44c584acb376d8
Author: Vyacheslav Daradur <[email protected]>
Date: 2017-05-31T08:41:56Z
ignite-5097: writing arrays length in varint encoding was implemented
----
> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> ----------------------------------------------------------------------------
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
> Issue Type: Task
> Components: general
> Affects Versions: 2.0
> Reporter: Vladimir Ozerov
> Assignee: Vyacheslav Daradur
> Labels: important, performance
> Fix For: 2.1
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
