[
https://issues.apache.org/jira/browse/IGNITE-11857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852833#comment-16852833
]
Aleksey Plekhanov commented on IGNITE-11857:
--------------------------------------------
[~ascherbakov] can you provide full parameters (benchmark.properties and
ignite-config.xml files) of scenarios where you got a performance drop?
I've run some benchmarks with these scenarios but didn't see any notable
performance drop.
Also, I've profiled code with different ignite/cache/transactions settings and
again didn't get any drop. According to my measures, new counters
implementation is not resource-consuming and transaction spend no more than
0.5% of the time in "update counter" methods.
> Investigate performance drop after IGNITE-10078
> -----------------------------------------------
>
> Key: IGNITE-11857
> URL: https://issues.apache.org/jira/browse/IGNITE-11857
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexei Scherbakov
> Assignee: Aleksey Plekhanov
> Priority: Major
>
> After IGNITE-10078 yardstick tests show performance drop up to 8% in some
> scenarios:
> * tx-optim-repRead-put-get
> * tx-optimistic-put
> * tx-putAll
> Partially this is due new update counter implementation, but not only.
> Investigation is required.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
