# Elasticsearch with disks cache on SSD

**URL:** <https://discuss.elastic.co/t/elasticsearch-with-disks-cache-on-ssd/46044>\
**Category:** Elasticsearch\
**Created:** [April 1, 2016, 10:58am UTC](https://discuss.elastic.co/t/elasticsearch-with-disks-cache-on-ssd/46044 "2016-04-01T10:58:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vincent\_gromakowski](https://avatars.discourse-cdn.com/v4/letter/v/59ef9b/32.png) [@vincent\_gromakowski](https://discuss.elastic.co/u/vincent_gromakowski)\
**Post date:** [April 1, 2016, 10:58am UTC](https://discuss.elastic.co/t/elasticsearch-with-disks-cache-on-ssd/46044/1 "2016-04-01T10:58:03Z")

</div>

I am looking for way to optimize read and agregations latency when using kibana over large number of documents.  
I have seen using SSD is a good option but out of budget, so I am looking for a way to use some kind of tiering with few SSD caching hot data from HDD.  
I have identified two solutions and would like to get opinions from you and if you have any experience using them:

- use ZFS with L2ARC functionality
- use Rapiddisk/Rapidcache Linux kernel module  
Any opinion ? Constraints ? REX ?  
Thanks

---

<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:** [July 5, 2017, 11:03pm UTC](https://discuss.elastic.co/t/elasticsearch-with-disks-cache-on-ssd/46044/2 "2017-07-05T23:03:20Z")

</div>