[jira] [Updated] (IGNITE-11115) Binary: rework thread-local binary context to avoid set() operation
[ https://issues.apache.org/jira/browse/IGNITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5: - Labels: performance (was: ) > Binary: rework thread-local binary context to avoid set() operation > --- > > Key: IGNITE-5 > URL: https://issues.apache.org/jira/browse/IGNITE-5 > Project: Ignite > Issue Type: Task > Components: binary >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Labels: performance > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we call {{ThreadLocal.set()}} on every > serialization/deserialization (see {{GridBinaryMarshaller#BINARY_CTX}} > usages). This may lead to high CPU usage, especially during SQL query > execution. > Let's refactor access patterns to work only with {{ThreadLocal.get()}} > operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11115) Binary: rework thread-local binary context to avoid set() operation
[ https://issues.apache.org/jira/browse/IGNITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-5: - Ignite Flags: (was: Docs Required) > Binary: rework thread-local binary context to avoid set() operation > --- > > Key: IGNITE-5 > URL: https://issues.apache.org/jira/browse/IGNITE-5 > Project: Ignite > Issue Type: Task > Components: binary >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Labels: performance > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently we call {{ThreadLocal.set()}} on every > serialization/deserialization (see {{GridBinaryMarshaller#BINARY_CTX}} > usages). This may lead to high CPU usage, especially during SQL query > execution. > Let's refactor access patterns to work only with {{ThreadLocal.get()}} > operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)