2015-11-20 13:57:28 -05:00
|
|
|
[[es-release-notes]]
|
2018-09-27 11:36:18 -04:00
|
|
|
= Release notes
|
2015-11-20 13:57:28 -05:00
|
|
|
|
|
|
|
|
[partintro]
|
|
|
|
|
--
|
2017-08-16 15:12:44 -04:00
|
|
|
|
2017-05-05 06:39:41 -04:00
|
|
|
This section summarizes the changes in each release.
|
|
|
|
|
|
2020-10-15 03:38:43 -04:00
|
|
|
* <<release-notes-7.10.0>>
|
2020-10-21 17:05:08 -04:00
|
|
|
* <<release-notes-7.9.3>>
|
2020-10-16 12:18:36 -04:00
|
|
|
* <<release-notes-7.9.2>>
|
2020-09-04 08:53:16 -04:00
|
|
|
* <<release-notes-7.9.1>>
|
2020-06-18 13:54:23 -04:00
|
|
|
* <<release-notes-7.9.0>>
|
2020-07-07 14:50:09 -04:00
|
|
|
* <<release-notes-7.8.1>>
|
value_count Aggregation optimization (backport of #54854) (#55076)
We found some problems during the test.
Data: 200Million docs, 1 shard, 0 replica
hits | avg | sum | value_count |
----------- | ------- | ------- | ----------- |
20,000 | .038s | .033s | .063s |
200,000 | .127s | .125s | .334s |
2,000,000 | .789s | .729s | 3.176s |
20,000,000 | 4.200s | 3.239s | 22.787s |
200,000,000 | 21.000s | 22.000s | 154.917s |
The performance of `avg`, `sum` and other is very close when performing
statistics, but the performance of `value_count` has always been poor,
even not on an order of magnitude. Based on some common-sense knowledge,
we think that `value_count` and sum are similar operations, and the time
consumed should be the same. Therefore, we have discussed the agg
of `value_count`.
The principle of counting in es is to traverse the field of each
document. If the field is an ordinary value, the count value is
increased by 1. If it is an array type, the count value is increased
by n. However, the problem lies in traversing each document and taking
out the field, which changes from disk to an object in the Java
language. We summarize its current problems with Elasticsearch as:
- Number cast to string overhead, and GC problems caused by a large
number of strings
- After the number type is converted to string, sorting and other
unnecessary operations are performed
Here is the proof of type conversion overhead.
```
// Java long to string source code, getChars is very time-consuming.
public static String toString(long i) {
int size = stringSize(i);
if (COMPACT_STRINGS) {
byte[] buf = new byte[size];
getChars(i, size, buf);
return new String(buf, LATIN1);
} else {
byte[] buf = new byte[size * 2];
StringUTF16.getChars(i, size, buf);
return new String(buf, UTF16);
}
}
```
test type | average | min | max | sum
------------ | ------- | ---- | ----------- | -------
double->long | 32.2ns | 28ns | 0.024ms | 3.22s
long->double | 31.9ns | 28ns | 0.036ms | 3.19s
long->String | 163.8ns | 93ns | 1921 ms | 16.3s
particularly serious.
Our optimization code is actually very simple. It is to manage different
types separately, instead of uniformly converting to string unified
processing. We added type identification in ValueCountAggregator, and
made special treatment for number and geopoint types to cancel their
type conversion. Because the string type is reduced and the string
constant is reduced, the improvement effect is very obvious.
hits | avg | sum | value_count | value_count | value_count | value_count | value_count | value_count |
| | | double | double | keyword | keyword | geo_point | geo_point |
| | | before | after | before | after | before | after |
----------- | ------- | ------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- |
20,000 | 38s | .033s | .063s | .026s | .030s | .030s | .038s | .015s |
200,000 | 127s | .125s | .334s | .078s | .116s | .099s | .278s | .031s |
2,000,000 | 789s | .729s | 3.176s | .439s | .348s | .386s | 3.365s | .178s |
20,000,000 | 4.200s | 3.239s | 22.787s | 2.700s | 2.500s | 2.600s | 25.192s | 1.278s |
200,000,000 | 21.000s | 22.000s | 154.917s | 18.990s | 19.000s | 20.000s | 168.971s | 9.093s |
- The results are more in line with common sense. `value_count` is about
the same as `avg`, `sum`, etc., or even lower than these. Previously,
`value_count` was much larger than avg and sum, and it was not even an
order of magnitude when the amount of data was large.
- When calculating numeric types such as `double` and `long`, the
performance is improved by about 8 to 9 times; when calculating the
`geo_point` type, the performance is improved by 18 to 20 times.
2020-04-10 13:16:39 -04:00
|
|
|
* <<release-notes-7.8.0>>
|
2020-06-01 12:56:32 -04:00
|
|
|
* <<release-notes-7.7.1>>
|
2020-03-31 16:23:49 -04:00
|
|
|
* <<release-notes-7.7.0>>
|
2020-03-24 17:41:55 -04:00
|
|
|
* <<release-notes-7.6.2>>
|
2020-03-04 09:46:20 -05:00
|
|
|
* <<release-notes-7.6.1>>
|
2020-01-15 14:06:59 -05:00
|
|
|
* <<release-notes-7.6.0>>
|
2020-01-16 14:34:39 -05:00
|
|
|
* <<release-notes-7.5.2>>
|
2020-01-15 11:52:22 -05:00
|
|
|
* <<release-notes-7.5.1>>
|
2019-11-12 03:57:58 -05:00
|
|
|
* <<release-notes-7.5.0>>
|
2019-10-30 18:55:43 -04:00
|
|
|
* <<release-notes-7.4.2>>
|
2019-10-22 08:52:37 -04:00
|
|
|
* <<release-notes-7.4.1>>
|
2019-08-30 04:08:42 -04:00
|
|
|
* <<release-notes-7.4.0>>
|
2019-09-11 11:26:25 -04:00
|
|
|
* <<release-notes-7.3.2>>
|
2019-08-19 16:54:39 -04:00
|
|
|
* <<release-notes-7.3.1>>
|
2019-07-10 03:35:45 -04:00
|
|
|
* <<release-notes-7.3.0>>
|
2019-07-15 12:11:04 -04:00
|
|
|
* <<release-notes-7.2.1>>
|
2019-06-26 09:50:11 -04:00
|
|
|
* <<release-notes-7.2.0>>
|
2019-06-01 07:52:47 -04:00
|
|
|
* <<release-notes-7.1.1>>
|
2019-05-09 13:10:19 -04:00
|
|
|
* <<release-notes-7.1.0>>
|
2019-04-05 17:26:22 -04:00
|
|
|
* <<release-notes-7.0.0>>
|
2019-04-01 15:01:13 -04:00
|
|
|
* <<release-notes-7.0.0-rc2>>
|
2019-03-22 14:24:22 -04:00
|
|
|
* <<release-notes-7.0.0-rc1>>
|
2019-02-14 10:42:26 -05:00
|
|
|
* <<release-notes-7.0.0-beta1>>
|
2018-12-11 17:24:47 -05:00
|
|
|
* <<release-notes-7.0.0-alpha2>>
|
2017-08-16 15:12:44 -04:00
|
|
|
* <<release-notes-7.0.0-alpha1>>
|
2017-05-05 06:39:41 -04:00
|
|
|
|
2015-11-20 13:57:28 -05:00
|
|
|
--
|
2019-03-22 14:24:22 -04:00
|
|
|
|
2020-10-15 03:38:43 -04:00
|
|
|
include::release-notes/7.10.asciidoc[]
|
2020-06-18 13:54:23 -04:00
|
|
|
include::release-notes/7.9.asciidoc[]
|
value_count Aggregation optimization (backport of #54854) (#55076)
We found some problems during the test.
Data: 200Million docs, 1 shard, 0 replica
hits | avg | sum | value_count |
----------- | ------- | ------- | ----------- |
20,000 | .038s | .033s | .063s |
200,000 | .127s | .125s | .334s |
2,000,000 | .789s | .729s | 3.176s |
20,000,000 | 4.200s | 3.239s | 22.787s |
200,000,000 | 21.000s | 22.000s | 154.917s |
The performance of `avg`, `sum` and other is very close when performing
statistics, but the performance of `value_count` has always been poor,
even not on an order of magnitude. Based on some common-sense knowledge,
we think that `value_count` and sum are similar operations, and the time
consumed should be the same. Therefore, we have discussed the agg
of `value_count`.
The principle of counting in es is to traverse the field of each
document. If the field is an ordinary value, the count value is
increased by 1. If it is an array type, the count value is increased
by n. However, the problem lies in traversing each document and taking
out the field, which changes from disk to an object in the Java
language. We summarize its current problems with Elasticsearch as:
- Number cast to string overhead, and GC problems caused by a large
number of strings
- After the number type is converted to string, sorting and other
unnecessary operations are performed
Here is the proof of type conversion overhead.
```
// Java long to string source code, getChars is very time-consuming.
public static String toString(long i) {
int size = stringSize(i);
if (COMPACT_STRINGS) {
byte[] buf = new byte[size];
getChars(i, size, buf);
return new String(buf, LATIN1);
} else {
byte[] buf = new byte[size * 2];
StringUTF16.getChars(i, size, buf);
return new String(buf, UTF16);
}
}
```
test type | average | min | max | sum
------------ | ------- | ---- | ----------- | -------
double->long | 32.2ns | 28ns | 0.024ms | 3.22s
long->double | 31.9ns | 28ns | 0.036ms | 3.19s
long->String | 163.8ns | 93ns | 1921 ms | 16.3s
particularly serious.
Our optimization code is actually very simple. It is to manage different
types separately, instead of uniformly converting to string unified
processing. We added type identification in ValueCountAggregator, and
made special treatment for number and geopoint types to cancel their
type conversion. Because the string type is reduced and the string
constant is reduced, the improvement effect is very obvious.
hits | avg | sum | value_count | value_count | value_count | value_count | value_count | value_count |
| | | double | double | keyword | keyword | geo_point | geo_point |
| | | before | after | before | after | before | after |
----------- | ------- | ------- | ----------- | ----------- | ----------- | ----------- | ----------- | ----------- |
20,000 | 38s | .033s | .063s | .026s | .030s | .030s | .038s | .015s |
200,000 | 127s | .125s | .334s | .078s | .116s | .099s | .278s | .031s |
2,000,000 | 789s | .729s | 3.176s | .439s | .348s | .386s | 3.365s | .178s |
20,000,000 | 4.200s | 3.239s | 22.787s | 2.700s | 2.500s | 2.600s | 25.192s | 1.278s |
200,000,000 | 21.000s | 22.000s | 154.917s | 18.990s | 19.000s | 20.000s | 168.971s | 9.093s |
- The results are more in line with common sense. `value_count` is about
the same as `avg`, `sum`, etc., or even lower than these. Previously,
`value_count` was much larger than avg and sum, and it was not even an
order of magnitude when the amount of data was large.
- When calculating numeric types such as `double` and `long`, the
performance is improved by about 8 to 9 times; when calculating the
`geo_point` type, the performance is improved by 18 to 20 times.
2020-04-10 13:16:39 -04:00
|
|
|
include::release-notes/7.8.asciidoc[]
|
2020-03-31 16:23:49 -04:00
|
|
|
include::release-notes/7.7.asciidoc[]
|
2020-01-15 14:06:59 -05:00
|
|
|
include::release-notes/7.6.asciidoc[]
|
2019-11-12 03:57:58 -05:00
|
|
|
include::release-notes/7.5.asciidoc[]
|
2019-08-30 04:08:42 -04:00
|
|
|
include::release-notes/7.4.asciidoc[]
|
2019-07-10 03:35:45 -04:00
|
|
|
include::release-notes/7.3.asciidoc[]
|
2019-06-26 09:50:11 -04:00
|
|
|
include::release-notes/7.2.asciidoc[]
|
2019-05-20 14:39:17 -04:00
|
|
|
include::release-notes/7.1.asciidoc[]
|
|
|
|
|
include::release-notes/7.0.asciidoc[]
|
2019-04-01 15:01:13 -04:00
|
|
|
include::release-notes/7.0.0-rc2.asciidoc[]
|
2019-03-22 14:24:22 -04:00
|
|
|
include::release-notes/7.0.0-rc1.asciidoc[]
|
2019-02-14 10:42:26 -05:00
|
|
|
include::release-notes/7.0.0-beta1.asciidoc[]
|
2018-12-11 17:24:47 -05:00
|
|
|
include::release-notes/7.0.0-alpha2.asciidoc[]
|
2017-08-16 15:12:44 -04:00
|
|
|
include::release-notes/7.0.0-alpha1.asciidoc[]
|
