New Rally `low-latency` challenge in `tsdb` track about elasticsearch HOT 5 OPEN

Pinging @elastic/es-storage-engine (Team:StorageEngine)

from elasticsearch.

I think 8.13-best-compression vs 8.14-best-compression would also be a good comparison.

from elasticsearch.

I need to re-run the tests above since they have errors. search_by_doc_id runs fine while get and mget fail, which is a bit surprising. I need to verify that assertions are enabled, because I would expect search_by_doc_id to fail too.

from elasticsearch.

Attaching test results
params-8-13-tsdb-low-latency-best-compression.json
params-8-13-tsdb-low-latency-best-speed.json
params-8-14-tsdb-low-latency-best-compression.json
params-8-14-tsdb-low-latency-best-speed.json

tsdb-low-latency-best_compression-8-13-vs-best_compression-8-14.txt
tsdb-low-latency-best_speed-8-13-vs-best_speed-8-14.txt

from elasticsearch.

Comparing the best compression option using Elasticsearch 8.13 and Elasticsearch 8.14 we can see results that seems a bit contradicting, with some GET queries being faster in 8.14 and other being slower (at higher latency percentiles). I think this is due to the fact that queries are very low latency queries taking less than 10 ms. This makes the test sensible to the environment and to test noise.

In the best speed scenario, intead, results seems to suggest that ZSTD is faster.

from elasticsearch.