[
https://issues.apache.org/jira/browse/IGNITE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Cherkasov updated IGNITE-5918:
--------------------------------------
Description:
Adding and searching objects in index tree produces a lot of garbage and this
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite
server spends about 15-25% CPU time in GC.
The problem is that ignite deserialize objects for comparing, while for the
primitive type and strings comparing can be implemented for bytes.
was:
Adding and searching objects in index tree produces a lot of garbage and this
can lead to big GC pauses.
Tests with data streaming of object with 5 string indexes show that ignite
server spends about 15-25% CPU time in GC.
The problem is that ignite desirialize objects for comparing
> Adding and searching objects in index tree produces a lot of garbage
> --------------------------------------------------------------------
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Cherkasov
> Assignee: Mikhail Cherkasov
>
> Adding and searching objects in index tree produces a lot of garbage and this
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite
> server spends about 15-25% CPU time in GC.
> The problem is that ignite deserialize objects for comparing, while for the
> primitive type and strings comparing can be implemented for bytes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
