phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (Jira)" <>
Subject [jira] [Assigned] (PHOENIX-5494) Batched, mutable Index updates are unnecessarily run one-by-one
Date Thu, 21 Nov 2019 19:10:00 GMT


Kadir OZDEMIR reassigned PHOENIX-5494:

    Assignee: chenglei  (was: Kadir OZDEMIR)

> Batched, mutable Index updates are unnecessarily run one-by-one
> ---------------------------------------------------------------
>                 Key: PHOENIX-5494
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Lars Hofhansl
>            Assignee: chenglei
>            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,
PHOENIX-5494_v6-4.x-HBase-1.4.patch, Screenshot_20191110_160243.png, Screenshot_20191110_160351.png,
>          Time Spent: 4h 50m
>  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

View raw message