You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2024/04/16 05:54:00 UTC

[jira] [Updated] (PHOENIX-7064) Prepare of local index mutations is extremely slow

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

Viraj Jasani updated PHOENIX-7064:
----------------------------------
    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> Prepare of local index mutations is extremely slow
> --------------------------------------------------
>
>                 Key: PHOENIX-7064
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7064
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.1.3
>            Reporter: fanartoria
>            Priority: Major
>             Fix For: 5.3.0, 5.1.4
>
>         Attachments: ddl-global.sql, ddl-local.sql, gen-data.sh, image-2023-10-09-17-29-47-856.png, image-2023-10-09-17-41-29-679.png, test-patch-using-global-index-logic.patch
>
>
> When the data table has more than one index, the prepare time of local index will be much slower than global index. 
> The write performance should be better on local indexes.
> Here is the stack trace which the most time is spent in.
> !image-2023-10-09-17-29-47-856.png!
> Seems a LocalTableState object will be create when prepare index mutation for each row.
> Compared with other ValueGetter, LazyValueGetter may be has bad performance.
> Why not use IndexMaintainer#createGetterFromKeyValues?
> Or combine the logic with global index prepare?



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