You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Kosarev (JIRA)" <ji...@apache.org> on 2018/05/23 15:47:00 UTC
[jira] [Updated] (IGNITE-8587) High Contention in
GridToStringBuilder.toStringImpl
[ https://issues.apache.org/jira/browse/IGNITE-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Kosarev updated IGNITE-8587:
-----------------------------------
Description:
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 instnace it shoots when DEBUG or TRACE logs are enabled as count of toString() invocations increases in this case massively.
We need to use ConcurrentHashMap instead and avoid global locks.
> 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
>
> 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 instnace it shoots when DEBUG or TRACE logs are enabled as count of toString() invocations increases in this case massively.
> We need to use ConcurrentHashMap instead and avoid global locks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)