[ 
https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120271#comment-16120271
 ] 

ASF GitHub Bot commented on IGNITE-5097:
----------------------------------------

GitHub user daradurvs opened a pull request:

    https://github.com/apache/ignite/pull/2425

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

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/daradurvs/ignite ignite-5736-module

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2425.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 #2425
    
----
commit efbac32e650d603e18ea405bee626589ac237f61
Author: Vyacheslav Daradur <dvsme...@gmail.com>
Date:   2017-08-09T14:05:29Z

    IGNITE-5732 Provide API to test compatibility with old releases (#20)

commit 0a7ffcce6527111a68568da0a6d22d4a1eb306a4
Author: Vyacheslav Daradur <dvsme...@gmail.com>
Date:   2017-08-09T14:09:08Z

    IGNITE-5097 BinaryMarshaller should write ints in "varint" encoding where 
it makes sense (#21)

commit 6b34d93609bc2087b77d7b44a0665ea160965e4e
Author: Vyacheslav Daradur <daradu...@gmail.com>
Date:   2017-08-09T17:08:50Z

    ignite-5736: added VarintArraysSizeCompatibilityTest

----


> 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.2
>
>
> 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.4.14#64029)

Reply via email to