[
https://issues.apache.org/jira/browse/IGNITE-22375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856237#comment-17856237
]
Aleksey Plekhanov commented on IGNITE-22375:
--------------------------------------------
JMH results:
{noformat}
Benchmark (ver) Mode Cnt
Score Error Units
JmhDirectByteBufferStreamBenchmark.writeReadIgniteUuid 3 thrpt 3
173729,589 ± 11265,776 ops/s
JmhDirectByteBufferStreamBenchmark.writeReadIgniteUuid 4 thrpt 3
582064,505 ± 4258,032 ops/s
JmhDirectByteBufferStreamBenchmark.writeReadUuid 3 thrpt 3
325306,801 ± 5562,056 ops/s
JmhDirectByteBufferStreamBenchmark.writeReadUuid 4 thrpt 3
1203484,342 ± 7195,944 ops/s
{noformat}
> 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 the are 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 it's required top 15 bits of {{{}long{}}}. Probability of such
> outcame for random long: 1/32768.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
