[
https://issues.apache.org/jira/browse/IGNITE-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630620#comment-16630620
]
Ivan Daschinskiy edited comment on IGNITE-9693 at 9/27/18 3:33 PM:
-------------------------------------------------------------------
[Latest TC
run|https://ci.ignite.apache.org/viewLog.html?buildId=1955602&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
[~ivan.glukos] Hi. I've reimplemented logic, now use brand new SegmentAware.
However, implementing the same logic for FsyncFileWALManager is not possible,
because this logic is not inserted here. Is it ok to create another ticket for
FsyncManager?
Nevertheless, waiting for new TC runAll()
was (Author: ivandasch):
[Latest|https://ci.ignite.apache.org/viewLog.html?buildId=1955602&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
[~ivan.glukos] Hi. I've reimplemented logic, now use brand new SegmentAware.
However, implementing the same logic for FsyncFileWALManager is not possible,
because this logic is not inserted here. Is it ok to create another ticket for
FsyncManager?
Nevertheless, waiting for new TC runAll()
> Scale up wal compression workers to increase performance
> --------------------------------------------------------
>
> Key: IGNITE-9693
> URL: https://issues.apache.org/jira/browse/IGNITE-9693
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Kosarev
> Assignee: Ivan Daschinskiy
> Priority: Major
> Fix For: 2.8
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
