[
https://issues.apache.org/jira/browse/IGNITE-9784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641736#comment-16641736
]
ASF GitHub Bot commented on IGNITE-9784:
----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/4924
IGNITE-9784 Automatically adjust max WAL history size
…mance drop
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9784
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4924.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4924
----
commit 1eff3881e3459819d755ac5b591d73f18ba4253d
Author: Alexey Goncharuk <alexey.goncharuk@...>
Date: 2018-10-08T12:08:26Z
IGNITE-9784 Automatically adjust max WAL history size to avoid performance
drop
----
> Performance drop on sql yardstick benchmarks
> --------------------------------------------
>
> Key: IGNITE-9784
> URL: https://issues.apache.org/jira/browse/IGNITE-9784
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.7
> Reporter: Ilya Suntsov
> Assignee: Alexey Goncharuk
> Priority: Blocker
> Fix For: 2.7
>
> Attachments: Screen Shot 2018-10-03 at 4.52.22 PM.png
>
>
> Please take a look at the attachment.
> Grid configuration:
> * 4 servers / 8 clients
> * java 8
> * 64 threads, 60s warmup, 180s duration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
