[
https://issues.apache.org/jira/browse/IGNITE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215097#comment-16215097
]
Anton Vinogradov commented on IGNITE-6411:
------------------------------------------
[~vozerov],
I made benchmarks and results are:
2 servers, 1 client
16 threads -> 1 streamer
Non indexed
DEFAULT 317 seconds
LOG_ONLY 140 seconds
BACKGROUND 126 seconds
NONE 43 seconds
Indexed
DEFAULT 457 seconds
LOG_ONLY 207 seconds
BACKGROUND 162 seconds
NONE 58 seconds
> 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)
