[
https://issues.apache.org/jira/browse/IGNITE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200390#comment-16200390
]
Vladimir Ozerov commented on IGNITE-6411:
-----------------------------------------
I would start work on this ticket from quick and dirty evaluation of potential
benefits. We need to design some adequate model with 10-20 fields of common
types (e.g. long, String). Then we should load many millions of key-value pairs
through data streamer to a bare-metal cluster with several severs. Need to
measure total load duration. I see 8 test modes:
1) 4 WAL modes
2) With and without additional indexes - this is very important thing, as even
1-2 additional index might give significant increase in IO operations.
> 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)
