[jira] [Comment Edited] (IGNITE-6411) Add ability to disable WAL for ceratin caches in runtime

["Alexey Goncharuk (JIRA)" <ji...@apache.org>]

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

Alexey Goncharuk edited comment on IGNITE-6411 at 10/25/17 11:49 AM:
---------------------------------------------------------------------

At stage one we can also adjust checkpoint triggering on 'too many dirty pages' to avoid early checkpoint starts. This, however, is an additional optimization and I would not implement it right away.


was (Author: agoncharuk):
At stage one we can also adjust checkpoint triggering on 'too many dirty pages' to avoid early checkpoint starts

> Add ability to disable WAL for ceratin caches in runtime
> --------------------------------------------------------
>
>                 Key: IGNITE-6411
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6411
>             Project: Ignite
>          Issue Type: Task
>          Components: persistence
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>            Assignee: Anton Vinogradov
>              Labels: iep-1, performance
>
> Currently every cache update require write to WAL. When doing bulk data load usually crash recovery is not needed. If something went wrong during data load, we should simply purge all intermediate data on cache restart.
> It makes sense to add ability to disable WAL for ceratin caches. Depending on restrictions of current architecture, it could be done on per-cache, per-cache-group or per-memory-policy level.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)