You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2024/04/04 09:34:00 UTC
[jira] [Updated] (IGNITE-21721) Sql. Adjust cost estimation for index scan
[ https://issues.apache.org/jira/browse/IGNITE-21721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Orlov updated IGNITE-21721:
--------------------------------------
Description:
Scan over an index if significantly slower than scan over a table. In some cases (for example, TPC-H q1 on scaleFactor=0.1) it's faster to read an entire table and do sorting in memory rather than scan the index.
Let's adjust cost function to reflect the real complexity of index scan.
was:
Scan over an index if significantly slower than scan over a table. In some cases (for example, TPC-H q4 on scaleFactor=0.1) it's faster to read an entire table and do sorting in memory rather than scan the index.
Let's adjust cost function to reflect the real complexity of index scan.
> Sql. Adjust cost estimation for index scan
> ------------------------------------------
>
> Key: IGNITE-21721
> URL: https://issues.apache.org/jira/browse/IGNITE-21721
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> Scan over an index if significantly slower than scan over a table. In some cases (for example, TPC-H q1 on scaleFactor=0.1) it's faster to read an entire table and do sorting in memory rather than scan the index.
> Let's adjust cost function to reflect the real complexity of index scan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)