ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-8587) High Contention in GridToStringBuilder.toStringImpl
Date Wed, 06 Jun 2018 09:25:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexey Goncharuk updated IGNITE-8587:
-------------------------------------
    Fix Version/s: 2.6

> High Contention in GridToStringBuilder.toStringImpl  
> -----------------------------------------------------
>
>                 Key: IGNITE-8587
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8587
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: Sergey Kosarev
>            Assignee: Sergey Kosarev
>            Priority: Major
>             Fix For: 2.6
>
>
> org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache implemented as 
> ordinal HashMap with all operations syncronised by one ReadWriteLock.
> this can trigger high contention as this class widely used in toString() methods.
> For instance it shoots when DEBUG or TRACE logs are  enabled as count of toString()
invocations increases in this case extremely.
> We need to use ConcurrentHashMap instead and avoid global locks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message