hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feng Honghua (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10487) Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing(old) values
Date Sat, 08 Feb 2014 11:45:19 GMT

     [ https://issues.apache.org/jira/browse/HBASE-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Feng Honghua updated HBASE-10487:
---------------------------------

    Description: in HRegion.append, new KeyValues will be allocated and do according bytes-copying
no matter whether there are existing kv for the appended cells, we can improve here by avoiding
the allocating of new KeyValue and according bytes-copying for kv which don't have existing(old)
values by reusing the passed-in kv and only updating its timestamp to 'now'(its original timestamp
is latest, so can be updated)  (was: in HRegion.append, a new KeyValue will be allocated no
matter there is existing kv for the appended cell, we can improve here by avoiding the allocating
of new KeyValue and according bytes-copying for kv which don't have existing(old) values by
reusing the passed-in kv and only updating its timestamp to 'now'(its original timestamp is
latest, so can be updated))

> Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't
have existing(old) values
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-10487
>                 URL: https://issues.apache.org/jira/browse/HBASE-10487
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Feng Honghua
>            Assignee: Feng Honghua
>         Attachments: HBASE-10487-trunk_v1.patch
>
>
> in HRegion.append, new KeyValues will be allocated and do according bytes-copying no
matter whether there are existing kv for the appended cells, we can improve here by avoiding
the allocating of new KeyValue and according bytes-copying for kv which don't have existing(old)
values by reusing the passed-in kv and only updating its timestamp to 'now'(its original timestamp
is latest, so can be updated)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message