Hey guys, we have mounted an btrfs file system with the compression method "zlib" for testing purposes on our elasticsearchserver and copied one of the indices on the btrfs volume, unfortunately it had no success and still got the size of 50gb :/
I will further try it with other compression methods and will report here Am Samstag, 19. Juli 2014 07:21:20 UTC+2 schrieb Otis Gospodnetic: > > Hi Horst, > > I wouldn't bother with this for the reasons Joerg mentioned, but should > you try it anyway, I'd love to hear your findings/observations. > > Otis > -- > Performance Monitoring * Log Analytics * Search Analytics > Solr & Elasticsearch Support * http://sematext.com/ > > > > On Wednesday, July 16, 2014 6:56:36 AM UTC-4, horst knete wrote: >> >> Hey Guys, >> >> to save a lot of hard disk space, we are going to use an compression file >> system, which allows us transparent compression for the es-indices. (It >> seems like es-indices are very good compressable, got up to 65% >> compression-rate in some tests). >> >> Currently the indices are laying at a ext4-Linux Filesystem which >> unfortunately dont have the transparent compression ability. >> >> Anyone of you got experience with compression file systems like BTRFS or >> ZFS/OpenZFS and can tell us if this led to big performance losses? >> >> Thanks for responding >> > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5fab716e-dcef-4edf-b658-56922f8dee16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
