[
https://issues.apache.org/jira/browse/FLINK-8922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395198#comment-16395198
]
Sihua Zhou commented on FLINK-8922:
-----------------------------------
[~StephanEwen] About the costs with (or without) WAL, I did have some tests for
that (On my macbook (ssd)):
{code}
---->number of records = 1000
disable WAL cost:7 ms
enable WAL cost:17 ms
---->
---->number of records = 10000
disable WAL cost:46 ms
enable WAL cost:153 ms
---->
---->number of records = 100000
disable WAL cost:1111 ms
enable WAL cost:1378 ms
---->
---->number of records = 1000000
disable WAL cost:3865 ms
enable WAL cost:9347 ms
---->
---->number of records = 10000000
disable WAL cost:36861 ms
enable WAL cost:97916 ms
---->
{code}
> Revert FLINK-8859 because it causes segfaults in testing
> --------------------------------------------------------
>
> Key: FLINK-8922
> URL: https://issues.apache.org/jira/browse/FLINK-8922
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.5.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Fix For: 1.5.0
>
>
> We need to revert FLINK-8859 because it causes problems with RocksDB that
> make our automated tests fail on Travis. The change looks actually good and
> it is currently unclear why this can introduce such a problem. This might
> also be a Rocks in RocksDB. Nevertheless, for the sake of a proper release
> testing, we should revert the change for now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
