[
https://issues.apache.org/jira/browse/HBASE-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810628#comment-13810628
]
Nicolas Liochon commented on HBASE-9869:
----------------------------------------
Yeah, I agree. There is always a risk. Still the logic seems strange to me. I'm
not sure the soft reference is still useful in 2013 :-). And removing the
synchronized seems better. I'm looking for a quick hack to see if there is a
difference.
> 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
>
>
> 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)
