ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-2409) Is CU.clientNode() really needed?
Date Wed, 02 Mar 2016 11:14:18 GMT

     [ 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)

Mime
View raw message