# Performance upgrade in server logs, but degrade in full text search

**URL:** <https://discuss.elastic.co/t/performance-upgrade-in-server-logs-but-degrade-in-full-text-search/287257>\
**Category:** Elasticsearch\
**Created:** [October 21, 2021, 7:23am UTC](https://discuss.elastic.co/t/performance-upgrade-in-server-logs-but-degrade-in-full-text-search/287257 "2021-10-21T07:23:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vsop\_479](https://avatars.discourse-cdn.com/v4/letter/v/6f9a4e/32.png) [@vsop\_479](https://discuss.elastic.co/u/vsop_479)\
**Post date:** [October 21, 2021, 7:23am UTC](https://discuss.elastic.co/t/performance-upgrade-in-server-logs-but-degrade-in-full-text-search/287257/1 "2021-10-21T07:23:08Z")

</div>

According to Elasticsearch benchmarks, ES 7.15.0 became slower than ES 6.8.14 in term, pharse, mothly\_agg queris in pmc track, but faster in most of queries (except hourly\_agg) in http logs track.  
So, which changes of Elasticsearch or lucene make the degrade in full text search and upgrade in http-logs?  
[https://elasticsearch-benchmarks.elastic.co/#tracks/pmc/release](https://elasticsearch-benchmarks.elastic.co/#tracks/pmc/release)  
[https://elasticsearch-benchmarks.elastic.co/#tracks/http-logs/release](https://elasticsearch-benchmarks.elastic.co/#tracks/http-logs/release)

PS:  
It makes no sense that es7 use less heap memory (index files off heap), but take a longer gc time.

```auto
es 7.15.0:
| Total Young Gen GC time | | 2.31 | s |
| Total Young Gen GC count | | 73 | |
| Total Old Gen GC time | | 0 | s |
| Total Old Gen GC count | | 0 | |
| Store size | | 19.1106 | GB |
| Translog size | | 3.07336e-07 | GB |
| Heap used for segments | | 0.417774 | MB |
| Heap used for doc values | | 0.0691032 | MB |
| Heap used for terms | | 0.238342 | MB |
| Heap used for norms | | 0.0405884 | MB |
| Heap used for points | | 0 | MB |
| Heap used for stored fields | | 0.0697403 | MB |

es6.8.20:
| Total Young Gen GC time | | 0.936 | s |
| Total Young Gen GC count | | 59 | |
| Total Old Gen GC time | | 0 | s |
| Total Old Gen GC count | | 0 | |
| Store size | | 20.3933 | GB |
| Translog size | | 2.67861 | GB |
| Heap used for segments | | 20.3588 | MB |
| Heap used for doc values | | 0.114174 | MB |
| Heap used for terms | | 18.3177 | MB |
| Heap used for norms | | 0.0384521 | MB |
| Heap used for points | | 0.00925446 | MB |
| Heap used for stored fields | | 1.87921 | MB |

```

---

<div class="post-metadata">

**Author:** ![vsop\_479](https://avatars.discourse-cdn.com/v4/letter/v/6f9a4e/32.png) [@vsop\_479](https://discuss.elastic.co/u/vsop_479)\
**Post date:** [October 28, 2021, 12:45pm UTC](https://discuss.elastic.co/t/performance-upgrade-in-server-logs-but-degrade-in-full-text-search/287257/3 "2021-10-28T12:45:45Z")

</div>

Preset dictionary impacting fetch time.

> **[Save space and money with improved storage efficiency in Elasticsearch 7.10](https://www.elastic.co/blog/save-space-and-money-with-improved-storage-efficiency-in-elasticsearch-7-10)**
>
> Elasticsearch 7.10 and Lucene 8.7 have made exciting improvements to boost storage efficiency. Indices created by our Elastic Observability and Elastic Security solutions are getting up to 10% smaller, which translates into direct cost savings for...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 25, 2021, 12:46pm UTC](https://discuss.elastic.co/t/performance-upgrade-in-server-logs-but-degrade-in-full-text-search/287257/4 "2021-11-25T12:46:36Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.