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

Posted to issues-all@impala.apache.org by "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2024/11/27 15:39:00 UTC

[jira] [Resolved] (IMPALA-13088) Speedup IcebergDeleteBuilder

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

Zoltán Borók-Nagy resolved IMPALA-13088.
----------------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> Speedup IcebergDeleteBuilder
> ----------------------------
>
>                 Key: IMPALA-13088
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13088
>             Project: IMPALA
>          Issue Type: Improvement
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Zoltán Borók-Nagy
>            Priority: Major
>              Labels: impala-iceberg
>             Fix For: Impala 4.5.0
>
>
> When there are lots of delete records IcebergDeleteBuilder can become a bottleneck. Since the left side of the JOIN is blocked on the build side any improvement we make here significantly improves Iceberg V2 table scanning.
> * std vector growths need lots of re-allocations and memory copies
> * inserting into the position vectors one-by-one is inefficient
> * sorting the position vectors could be parallelized (especially in case of MT_DOP when there are MT_DOP threads blocked on the build)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org