You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2025/11/25 10:34:00 UTC

[jira] [Updated] (IGNITE-27166) Optimize ascii strings comparison

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

Ivan Bessonov updated IGNITE-27166:
-----------------------------------
    Component/s: secondary indexes ai3

> Optimize ascii strings comparison
> ---------------------------------
>
>                 Key: IGNITE-27166
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27166
>             Project: Ignite
>          Issue Type: Improvement
>          Components: secondary indexes ai3
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {color:#172b4d}In {color}{{BinaryTupleComparatorUtils}} we should use the same optimization for {{compareAsciiSequences}} that we have in {{{}compareAsBytes{}}}. It should help us increasing an overall performance of sorted indexes, and possibly other places too.
> NOTE: such an optimization is not possible for case-insensitive comparison. But, we don't actually use it, so I propose completely deleting {{ignoreCase}} flag from that code until we actually need it.



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