You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Lars Hofhansl (Jira)" <ji...@apache.org> on 2019/11/14 22:40:00 UTC
[jira] [Comment Edited] (PHOENIX-5494) Batched, mutable Index
updates are unnecessarily run one-by-one
[ https://issues.apache.org/jira/browse/PHOENIX-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974645#comment-16974645 ]
Lars Hofhansl edited comment on PHOENIX-5494 at 11/14/19 10:39 PM:
-------------------------------------------------------------------
.003 is nice improvement! For large batches it cuts about about 50% of the end-to-end time (all with default settings and testing on a single machine only); and it's never slower.
was (Author: lhofhansl):
.003 is nice improvement! For large batches it cuts about about 50% of the end-to-end time (all with default settings and testing on a single machine only).
> Batched, mutable Index updates are unnecessarily run one-by-one
> ---------------------------------------------------------------
>
> Key: PHOENIX-5494
> URL: https://issues.apache.org/jira/browse/PHOENIX-5494
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Assignee: Kadir OZDEMIR
> Priority: Major
> Labels: performance
> Attachments: PHOENIX-5494.master.001.patch, PHOENIX-5494.master.002.patch, PHOENIX-5494.master.003.patch, Screenshot_20191110_160243.png, Screenshot_20191110_160351.png, Screenshot_20191110_161453.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> I just noticed that index updates on mutable tables retrieve their deletes (to invalidate the old index entry) one-by-one.
> For batches, this can be *the* major time spent during an index update. The cost is mostly incured by the repeated setup (and seeking) of the new region scanner (for each row).
> We can instead do a skip scan and get all updates in a single scan per region.
> (Logically that is simple, but it will require some refactoring)
> I won't be getting to this, but recording it here in case someone feels inclined.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)