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/02/13 10:02:00 UTC

[jira] [Commented] (IGNITE-11297) Improving read of hot variables in WAL

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

Ignite TC Bot commented on IGNITE-11297:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3069516&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Improving read of hot variables in WAL
> --------------------------------------
>
>                 Key: IGNITE-11297
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11297
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Anton Kalashnikov
>            Assignee: Anton Kalashnikov
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Looks like it is not neccessery mark some variables as volatile in FileWriteAheadLogManager because its initialized only one time on start but its have a lot of read of them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)