[
https://issues.apache.org/jira/browse/HBASE-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-13894:
------------------------------------
Comment: was deleted
(was: v0 is better in perf/contention that what we have currently, but is not
the optimal solution. if we can get rid of that map and have a custom one we
will avoid the double lock map + entry semaphore, and we can get rid of that
while true with the deleted flag)
> Avoid visitor alloc each call of ByteBufferArray get/putMultiple()
> ------------------------------------------------------------------
>
> Key: HBASE-13894
> URL: https://issues.apache.org/jira/browse/HBASE-13894
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 2.0.0, 1.0.1, 1.1.0
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.1.1
>
> Attachments: HBASE-13894-v0.patch
>
>
> ByteBufferArray getMultiple()/putMultiple() creates a new Visitor each call.
> we can move that visitor out.
> also, ByteBufferArray.multiple() seems to be an hotspot, I tried to do some
> experiments using slice and read/write lock instead of a mutex, doesn't seems
> to change much. any thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
