[ https://issues.apache.org/jira/browse/IGNITE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114324#comment-16114324 ]
ASF GitHub Bot commented on IGNITE-5918: ---------------------------------------- GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/2398 IGNITE-5918 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5918 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2398.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2398 ---- commit 8909ef69ab03c37b1bf99e25335b6f385f1ebbc3 Author: Igor Seliverstov <gvvinbl...@gmail.com> Date: 2017-08-04T12:45:01Z IGNITE-5918 Adding and searching objects in index tree produces a lot of garbage ---- > 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)