tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Xiaoman Huang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-247) Avoid encoding the transaction multiple times
Date Tue, 16 Jan 2018 08:39:00 GMT

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

Patrick Xiaoman Huang commented on TEPHRA-247:
----------------------------------------------

Hi Andreas,

Agree as you described the scenario, my proposal seems little too complex and not that convincing.

and agree that if we can avoid invalid list transfering that will be much less bytes to transfer.

Another question, if there are many clients, will inProgress in tx  be large?

Thanks

Patrick

> Avoid encoding the transaction multiple times
> ---------------------------------------------
>
>                 Key: TEPHRA-247
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-247
>             Project: Tephra
>          Issue Type: Improvement
>          Components: core, manager
>    Affects Versions: 0.12.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Andreas Neumann
>            Priority: Major
>         Attachments: design.jpg
>
>
> Currently, the same transaction object is encoded again and again for every Get performed
in HBase. It would be better to cache the encoded transaction for the duration of the transaction
and reuse it, 



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

Mime
View raw message