[
https://issues.apache.org/jira/browse/HBASE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823044#comment-13823044
]
stack commented on HBASE-9869:
------------------------------
Patch should remove softsortedvaluemap too while you are at it.
Numbers look good.
On the middle approach, we'd drop unused tables. That could help.
Anyway to get deepsize of the Map? If it were > some %age of the heap, we
could just run a clean or purge of it as a precaution against leaks or OOME'ing
on big cluster. Would that be hard to do?
> Optimize HConnectionManager#getCachedLocation
> ---------------------------------------------
>
> Key: HBASE-9869
> URL: https://issues.apache.org/jira/browse/HBASE-9869
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9869.v1.patch, 9869.v1.patch, 9869.v2.patch
>
>
> It javadoc says: "TODO: This method during writing consumes 15% of CPU doing
> lookup". This is still true, says Yourkit. With 0.96, we also spend more time
> in these methods. We retry more, and the AsyncProcess calls it in parallel.
> I don't have the patch for this yet, but I will spend some time on it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
