Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How about enabling index.codec DEFLATE ? #650

Closed
southerncomputer opened this issue Dec 6, 2017 · 3 comments
Closed

How about enabling index.codec DEFLATE ? #650

southerncomputer opened this issue Dec 6, 2017 · 3 comments
Labels
Milestone

Comments

@southerncomputer
Copy link
Contributor

index.codec
The default value compresses stored data with LZ4 compression, but this can be set to best_compression which uses DEFLATE for a higher compression ratio, at the expense of slower stored fields performance. If you are updating the compression type, the new one will be applied after segments are merged. Segment merging can be forced using force merge.

I wonder what kind of storage savings we'd see with this option?

https://www.elastic.co/blog/elasticsearch-storage-the-true-story-2.0

@afoucret
Copy link
Contributor

We did not evaluate this option.
Do you have any speed (indexing and query) and index size benchmarks on your setup (I know it is a quite big catalog).

@southerncomputer
Copy link
Contributor Author

15% saved - i have 48 cores and 128gb of ram - time to full reindex 2m products 1h:45m - 15% * 2 is a good bit of SSD that costs a lot more than cpu/ram ..

@afoucret
Copy link
Contributor

PR #663 use the best_compression for indices created with ElasticSuite.

Will be part of the next stable release (2.5.0).

@afoucret afoucret added this to the 2.5 milestone Jan 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants