[
https://issues.apache.org/jira/browse/IGNITE-22559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-22559:
-----------------------------------
Description:
# We should benchmark readInt / readLong against protobuf, since it uses the
same binary format
# We should create much faster way of creating deserializers for messages. For
example, we could generate "switch" statements like in Ignite 2. Both for
creating message deserializer (compile time generation) and for message group
deserialization factory (runtime generation, because we don't know the list of
factories)
# We should get rid of serializers and deserializers as separate classes and
move generated code into message implementation. This way we save on
allocations and we don't create builder, which is also expensive, we should
write directly into fields of target object like in Ignite 2.
> Optimize raft command deserialization
> -------------------------------------
>
> Key: IGNITE-22559
> URL: https://issues.apache.org/jira/browse/IGNITE-22559
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
>
> # We should benchmark readInt / readLong against protobuf, since it uses the
> same binary format
> # We should create much faster way of creating deserializers for messages.
> For example, we could generate "switch" statements like in Ignite 2. Both for
> creating message deserializer (compile time generation) and for message group
> deserialization factory (runtime generation, because we don't know the list
> of factories)
> # We should get rid of serializers and deserializers as separate classes and
> move generated code into message implementation. This way we save on
> allocations and we don't create builder, which is also expensive, we should
> write directly into fields of target object like in Ignite 2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
