# New logsdb format

**URL:** <https://discuss.elastic.co/t/new-logsdb-format/377101>\
**Category:** Elasticsearch\
**Created:** [April 14, 2025, 8:41am UTC](https://discuss.elastic.co/t/new-logsdb-format/377101 "2025-04-14T08:41:50Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![skeyby](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skeyby/32/142612_2.png) [@skeyby](https://discuss.elastic.co/u/skeyby)\
**Post date:** [April 15, 2025, 2:46pm UTC](https://discuss.elastic.co/t/new-logsdb-format/377101/21 "2025-04-15T14:46:31Z")

</div>

I have a TEST Cluster. It's not similar to the Production one but I can do some kind of _a/b_ testing between standard and logsdb index format and see the performance hit.

If you think it could be useful I can work on that tomorrow.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [April 15, 2025, 3:38pm UTC](https://discuss.elastic.co/t/new-logsdb-format/377101/22 "2025-04-15T15:38:23Z")

</div>

> [@skeyby](#):
>
> I have a TEST Cluster. It's not similar to the Production one but I can do some kind of _a/b_ testing between standard and logsdb index format and see the performance hit.
> 
> If you think it could be useful I can work on that tomorrow.

Yes that could be informative to help understand the issue.... BUT if the HW Profiles are substantially different say like SSD vs the HDD on prod it may not as much help...

It will only be useful if there are settings / adjustment that could be made to help your Production cluster, which I am not sure what other setting on the Logsdb side would have a positive / material affect.

> **[Logs data stream | Elastic documentation](https://www.elastic.co/docs/manage-data/data-store/data-streams/logs-data-stream)**
>
> A logs data stream is a data stream type that stores log data more efficiently. In benchmarks, log data stored in a logs data stream used ~2.5 times less...

or on the merge side (be careful with these settings)

> **[Merge settings | Elastic Documentation](https://www.elastic.co/docs/reference/elasticsearch/index-settings/merge)**
>
> A shard in Elasticsearch is a Lucene index, and a Lucene index is broken down into segments. Segments are internal storage elements in the index where...

Lets see if / when the others weigh in before "we" add work to your plate. 🙂

---

<div class="post-metadata">

**Author:** ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)\
**Post date:** [April 16, 2025, 5:38am UTC](https://discuss.elastic.co/t/new-logsdb-format/377101/23 "2025-04-16T05:38:38Z")

</div>

If you see the abnormal CPU usage, then hot thread dumps could be helpful to see what is the cause.

[Previous page](https://discuss.elastic.co/t/new-logsdb-format/377101.md?page=1)
