[ 
https://issues.apache.org/jira/browse/IGNITE-22561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirill Tkalenko updated IGNITE-22561:
-------------------------------------
    Description:  {{@Marshallable ByteString}} - this pattern became obsolete 
long time ago. {{ByteBuffer}} type is natively supported by the protocol, and 
it should eliminate unnecessary data copying, potentioally making the system 
faster.  (was: Here I would include two types of improvements:
 * {{@Marshallable ByteString}} - this pattern became obsolete long time ago. 
{{ByteBuffer}} type is natively supported by the protocol, and it should 
eliminate unnecessary data copying, potentioally making the system faster
 * Pretty much the same thing, but for {{{}byte[]{}}}. It's used in classes 
like {{{}org.apache.ignite.internal.metastorage.dsl.Operation{}}}. If we 
migrate these properties to {{ByteBuffer}} then deserialization will become 
significantly faster, but in order to utilize it we would have to change 
internal metastorage implementation a little bit (like optimizing memory usage 
in {{{}RocksDbKeyValueStorage#addDataToBatch{}}}).
If it requires too many changes then I propose doing it in a separate JIRA. My 
assumption - it will not require too many changes, but we'll see.)

> Get rid of ByteString in messages
> ---------------------------------
>
>                 Key: IGNITE-22561
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22561
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3, ignite3_performance
>             Fix For: 3.0.0-beta2
>
>
>  {{@Marshallable ByteString}} - this pattern became obsolete long time ago. 
> {{ByteBuffer}} type is natively supported by the protocol, and it should 
> eliminate unnecessary data copying, potentioally making the system faster.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to