You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2019/12/05 15:24:00 UTC
[jira] [Commented] (IGNITE-11857) Investigate performance drop
after IGNITE-10078
[ https://issues.apache.org/jira/browse/IGNITE-11857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988906#comment-16988906 ]
Ignite TC Bot commented on IGNITE-11857:
----------------------------------------
{panel:title=Branch: [pull/6686/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4812258&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Attachments: ignite-config.xml, run.properties.tx-optimistic-put-b-backup
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)