phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4762) Performance regression with transactional immutable indexes
Date Fri, 01 Jun 2018 06:53:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497647#comment-16497647
] 

James Taylor commented on PHOENIX-4762:
---------------------------------------

Please review, [~tdsilva]. There are two things that were broken:
 * We should not add index tables as transaction participants for Tephra. This would cause
all the index updates to be kept in memory which we don't need (since we can generate them).
 * Use the PhoenixTxIndexGenerator to generate the deletes from the client. The server only
handles index updates for local tables. The perf degradation from above was masking this issue
- we were essentially generating the deletes for index rows during rollback twice for global
indexes.

 

> Performance regression with transactional immutable indexes
> -----------------------------------------------------------
>
>                 Key: PHOENIX-4762
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4762
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>            Priority: Major
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4762_v1.patch
>
>
> The introduction of the TAL caused a performance regression with immutable indexes. Prior
to the TAL, index rows would not be transaction participants so they would not take up client
memory. Instead, on rollback, we re-generate the index deletes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message