[
https://issues.apache.org/jira/browse/IGNITE-22375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856261#comment-17856261
]
Ignite TC Bot commented on IGNITE-22375:
----------------------------------------
{panel:title=Branch: [pull/11364/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11364/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7921061&buildTypeId=IgniteTests24Java8_RunAll]
> Inefficient serialization of UUIDs in communication messages
> ------------------------------------------------------------
>
> Key: IGNITE-22375
> URL: https://issues.apache.org/jira/browse/IGNITE-22375
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We serialize {{long}} and {{int}} data types in communication messages as
> {{varint}} to safe the space. UUID contains two {{long}} components
> {{LeastSignificantBits}} and {{MostSignificantBits}}, which currently
> serialized as {{varint}} too. But usually UUIDs are generated randomly and in
> most cases there is no any space optimization for random {{long}} values. To
> store {{long}} as 7 bytes or less in {{varint}} format (instead of 8 bytes to
> store {{long}} as is) it's required top 15 bits of {{long}} to be 0.
> Probability of such outcame for random long: 1/32768.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
