[jira] [Commented] (IGNITE-11115) Binary: rework thread-local binary context to avoid set() operation

2019-01-29 Thread Ignite TC Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755802#comment-16755802
 ] 

Ignite TC Bot commented on IGNITE-5:


{panel:title=-- Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Restarts) 1{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2940133]]
* IgniteCacheRestartTestSuite: 
GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesNoBackups - 
0,0% fails in last 407 master runs.

{color:#d04437}Cache (Restarts) 2{color} [[tests 
6|https://ci.ignite.apache.org/viewLog.html?buildId=2940134]]
* IgniteCacheRestartTestSuite2: 
IgniteCacheAtomicPutAllFailoverSelfTest.testPutAllFailoverColocatedNearEnabledOneBackup
 - 0,0% fails in last 423 master runs.
* IgniteCacheRestartTestSuite2: 
IgniteCacheAtomicNodeRestartTest.testRestartWithPutEightNodesTwoBackups - 0,0% 
fails in last 423 master runs.
* IgniteCacheRestartTestSuite2: 
IgniteCacheAtomicNodeRestartTest.testRestartWithTxTwoNodesOneBackup - 0,0% 
fails in last 423 master runs.
* IgniteCacheRestartTestSuite2: 
IgniteCacheAtomicNodeRestartTest.testRestartWithTxSixNodesTwoBackups - 0,0% 
fails in last 423 master runs.
* IgniteCacheRestartTestSuite2: 
IgniteCacheAtomicNodeRestartTest.testRestartWithTxFourNodesOneBackups - 0,0% 
fails in last 423 master runs.

{color:#d04437}Data Structures{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=2940148]]
* IgniteCacheDataStructuresSelfTestSuite: 
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithTxTwoNodesOneBackup
 - 0,0% fails in last 434 master runs.
* IgniteCacheDataStructuresSelfTestSuite: 
GridCachePartitionedQueueApiSelfTest.testMultipleStructuresInDifferentGroups - 
0,0% fails in last 434 master runs.
* IgniteCacheDataStructuresSelfTestSuite: 
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups
 - 0,0% fails in last 434 master runs.
* IgniteCacheDataStructuresSelfTestSuite: 
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups
 - 0,0% fails in last 434 master runs.
* IgniteCacheDataStructuresSelfTestSuite: 
IgniteCacheAtomicReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups
 - 0,0% fails in last 434 master runs.

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2940188buildTypeId=IgniteTests24Java8_RunAll]

> 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] [Commented] (IGNITE-11115) Binary: rework thread-local binary context to avoid set() operation

2019-01-28 Thread Vladimir Ozerov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754705#comment-16754705
 ] 

Vladimir Ozerov commented on IGNITE-5:
--

Implemented. Test run: 
https://ci.ignite.apache.org/viewQueued.html?itemId=2940188

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