[IGNITE-5918] Adding and searching objects in index tree produces a lot of garbage

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.3
• Component/s: general
• Labels: performance
• Assignee: Igor Seliverstov
• Reporter: Mikhail Cherkasov
• Created: 03/Aug/17 11:03
• Updated: 01/Aug/19 22:06
• Resolved: 09/Aug/17 15:48

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.

Issue Links

• requires: IGNITE-6360 NPE occurs if object with null indexed field is added
• links to: GitHub Pull Request #2398
• links to: GitHub Pull Request #2398
• links to: TC run
• links to: upsource