Igniters, i`l try to compare 2.8 release candidate vs 2.7.6,
last sha 2.8 was build from : 9d114f3137f92aebc2562a
i use yardstick benchmarks, 4 bare machine with: 2x Xeon X5570 96Gb 512GB SSD
2048GB HDD 10GB/s
1 for client (driver) and 3 for servers.
this mappings for graphs and real yardstick tests:
atomic-put: IgnitePutBenchmark
sql-merge-query: IgniteSqlMergeQueryBenchmark
atomic-get: IgniteGetBenchmark
tx-get: IgniteGetTxBenchmark
tx-put: IgnitePutTxBenchmark
atomic-put-all-bs-10: IgnitePutAllBenchmark
tx-put-all-bs-10: IgnitePutAllTxBenchmark
cacheMode — partitioned
CacheWriteSynchronizationMode.FULL_SYNC
1 backup
1. wal = log_only 2. wal = none 3. persistence disabled.
Thanks Maxim for wiki page [1]
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks
do we need some bisect or other work here ?
>
>
>------- Forwarded message -------
>From: "Maxim Muzafarov" < mmu...@apache.org >
>To: dev@ignite.apache.org
>Cc:
>Subject: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]
>Date: Fri, 20 Sep 2019 14:44:31 +0300
>
>Igniters,
>
>
>It's almost a year has passed since the last major Apache Ignite 2.7
>has been released. We've accumulated a lot of performance improvements
>and a lot of new features which are waiting for their release date.
>Here is my list of the most interesting things from my point since the
>last major release:
>
>Service Grid,
>Monitoring,
>Recovery Read
>BLT auto-adjust,
>PDS compression,
>WAL page compression,
>Thin client: best effort affinity,
>Thin client: transactions support (not yet)
>SQL query history
>SQL statistics
>
>I think we should no longer wait and freeze the master branch anymore
>and prepare the next major release by the end of the year.
>
>
>I propose to discuss Time, Scope of Apache Ignite 2.8 release and also
>I want to propose myself to be the release manager of the planning
>release.
>
>Scope Freeze: November 4, 2019
>Code Freeze: November 18, 2019
>Voting Date: December 10, 2019
>Release Date: December 17, 2019
>
>
>WDYT?
