[
https://issues.apache.org/jira/browse/PHOENIX-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976325#comment-16976325
]
chenglei edited comment on PHOENIX-5494 at 11/18/19 10:19 AM:
--------------------------------------------------------------
[~kozdemir], thank you for the check, ok, I would try to rebase it.
Uploaded PHOENIX-5494_v3-4.x-HBase-1.4.patch which is rebased on PHOENIX-5565,
[~kozdemir], [~larsh] please have a review.
was (Author: comnetwork):
[~kozdemir], thank you for the check, ok, I would try to rebase it.
Uploaded PHOENIX-5494_v3-4.x-HBase-1.4.patch which is rebased on PHOENIX-5565
> 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: 5494-4.x-HBase-1.5.txt,
> PHOENIX-5494-4.x-HBase-1.4.patch, PHOENIX-5494.master.001.patch,
> PHOENIX-5494.master.002.patch, PHOENIX-5494.master.003.patch,
> PHOENIX-5494_v3-4.x-HBase-1.4.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)
