[ https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006066#comment-16006066 ]
Vyacheslav Daradur commented on IGNITE-5097: -------------------------------------------- [~isapego], I didn't implement it, because it isn't described in the task. If we implement a writing long/int64 in varint encoding, we will be able to use it at serializing for following types: {{Long}} (1 long), {{Date}} (1 long), {{Time}} (1 long), {{Timestamp}} (1 long), {{UUID}} (2 longs). I think there will be less proffit than in implemented varint, because long values usualy is big. ({{Date}}, {{Time}}, {{Timestamp}}, {{UUID}}). But it will allow us to use memory more effectively, it is always cool) [~vozerov], [~ptupitsyn], any thougths? > 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)