ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage
Date Mon, 07 Aug 2017 08:34:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116258#comment-16116258
] 

Vladimir Ozerov commented on IGNITE-5918:
-----------------------------------------

[~gvvinblade], looks good to me in general, but proposed improvement is not tested properly.
We need to add much more tests to cover various string scenarios, including 1 byte chars (Latin),
2 byte chars (e.g. Cyrillic), and 4-byte surrogate chars. 

> 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
>    Affects Versions: 2.1
>            Reporter: Mikhail Cherkasov
>            Assignee: Igor Seliverstov
>
> 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)

Mime
View raw message