honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add indexing speed improvement to the 7.10 release highlights (#63621) 

Add indexing speed improvement to the 7.10 release highlights

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
This commit is contained in:
Andrei Dan 2020-10-26 15:11:40 +00:00 committed by GitHub
parent e02561476e
commit 89e3a3178f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/reference/release-notes/highlights.asciidoc
View File

@ -25,6 +25,19 @@ Other versions:
// tag::notable-highlights[] // tag::notable-highlights[]
[discrete] [discrete]
[[indexing-speed-improvement]]
=== Indexing speed improvement
{es} 7.10 improves indexing speed by up to 20%. We've reduced the coordination
needed to add entries to the <<index-modules-translog,transaction log>>. This
reduction allows for more concurrency and increases the transaction log buffer
size from `8KB` to `1MB`. However, performance gains are lower for
full-text search and other analysis-intensive use cases. The heavier the
indexing chain, the lower the gains, so indexing chains that involve many
fields, ingest pipelines or full-text indexing will see lower gains.
[discrete]
[[more-space-efficient-indices]]
=== More space-efficient indices === More space-efficient indices
{es} 7.10 depends on Apache Lucene 8.7, which introduces higher compression of {es} 7.10 depends on Apache Lucene 8.7, which introduces higher compression of
@ -40,12 +53,11 @@ Elasticsearch offers the ability to configure the <<index-codec,`index.codec`>>
setting to tell Elasticsearch how aggressively to compress stored fields. Both setting to tell Elasticsearch how aggressively to compress stored fields. Both
supported values `default` and `best_compression` will get better compression supported values `default` and `best_compression` will get better compression
with this change. with this change.
// end::notable-highlights[]
// tag::notable-highlights[]
[discrete] [discrete]
[[data-tier-formalization]] [[data-tier-formalization]]
=== Data tiers === Data tiers
7.10 introduces the concept of formalized data tiers within Elasticsearch. <<data-tiers,Data tiers>> 7.10 introduces the concept of formalized data tiers within Elasticsearch. <<data-tiers,Data tiers>>
are a simple, integrated approach that gives users control over optimizing for cost, are a simple, integrated approach that gives users control over optimizing for cost,
performance, and breadth/depth of data. Prior to this formalization, many users configured their own performance, and breadth/depth of data. Prior to this formalization, many users configured their own