You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Description
Currently, the Apache Ignite 2.12 thread exists on dev-list.
Release Manager
Nikita Amelchev
Release phases
Scope Freeze: October 15, 2021
Code Freeze: December 2, 2021
Voting Date: December --, 2021
Release Date: December --, 2021
The most important release tasks
The most important tasks, features, optimizations, and fixes that have to get into the release.
Such tickets have to be labelled or marked with a Flag "important" in JIRA.
key |
summary |
type |
assignee |
reporter |
customfield_12311032 |
customfield_12311037 |
customfield_12311022 |
customfield_12311027 |
priority |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Resolved issues
key |
summary |
type |
updated |
assignee |
customfield_12311032 |
customfield_12311037 |
customfield_12311022 |
customfield_12311027 |
priority |
status |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
key |
summary |
type |
updated |
assignee |
customfield_12311032 |
customfield_12311037 |
customfield_12311022 |
customfield_12311027 |
priority |
status |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Documentation tasks for important features
key |
summary |
updated |
assignee |
customfield_12311032 |
customfield_12311037 |
customfield_12311022 |
customfield_12311027 |
priority |
status |
type |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
All unresolved documentation tasks
key |
summary |
updated |
assignee |
customfield_12311032 |
customfield_12311037 |
customfield_12311022 |
customfield_12311027 |
priority |
status |
type |
JQL and issue key arguments for this macro require at least one Jira application link to be configured
|
Release issues grouped by status
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Benchmarks
4 servers, 4 drivers, sm=PRIMARY_SYNC, wm=LOG_ONLY, b=1, t=50, j=10
In-memory (2.11 vs 2.12)
Benchmark name | TPS(%) | Latency(%) |
---|
IgnitePutBenchmark | 0,45 | -0,74 |
IgniteGetBenchmark | 1,47 | -1,48 |
IgnitePutTxImplicitBenchmark | 2,8 | -2,84 |
IgnitePutGetTxBenchmark -txc OPTIMISTIC | 0,5 | -0,55 |
IgnitePutGetTxBenchmark -txc PESSIMISTIC | -0,8 | 0,71 |
IgnitePutGetTxBenchmark -txc OPTIMISTIC -txi SERIALIZABLE | 2,94 | -2,71 |
IgniteSqlQueryBenchmark | -0,05 | 0,07 |
IgnitePutAllTxBenchmark -bs 100 | 0,69 | -0,65 |
IgnitePutAllBenchmark -bs 100 | 0,73 | -0,24 |
Persistence (2.11 vs 2.12)
Benchmark name | TPS(%) | Latency(%) |
---|
IgnitePutBenchmark | -0,3 | 0,4 |
IgniteGetBenchmark | -1,11 | 1,12 |
IgnitePutTxImplicitBenchmark | -2,02 | 2 |
IgnitePutGetTxBenchmark -txc OPTIMISTIC | -0,02 | 0,02 |
IgnitePutGetTxBenchmark -txc PESSIMISTIC | -0,01 | 0,01 |
IgnitePutGetTxBenchmark -txc OPTIMISTIC -txi SERIALIZABLE | -0,03 | 0,03 |
IgniteSqlQueryBenchmark | 1,35 | -1,36 |
IgnitePutAllTxBenchmark -bs 100 | -0,01 | 0,01 |
IgnitePutAllBenchmark -bs 100 | -0,51 | 0,48 |