You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/03/02 12:14:18 UTC
[jira] [Assigned] (IGNITE-2409) Is CU.clientNode() really needed?
[ https://issues.apache.org/jira/browse/IGNITE-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov reassigned IGNITE-2409:
---------------------------------------
Assignee: Vladimir Ozerov (was: Alexey Goncharuk)
> Is CU.clientNode() really needed?
> ---------------------------------
>
> Key: IGNITE-2409
> URL: https://issues.apache.org/jira/browse/IGNITE-2409
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Profiling shows medium hot spot in the method GridCacheUtils.clientNode(ClusterNode) - considerable amount of time is spent on attributes map lookup.
> What is interesting is that ClusterNode already has isClient() method which do not require any lookups.
> Can we simply remove GridCacheUtils.clientNode() method and use ClusterNode.isClient() instead?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)