On Sun, Mar 15, 2015 at 2:03 PM, Ali Akhtar <ali.rac...@gmail.com> wrote:
> I was watching a talk recently on Elasticsearch performance in EC2, and > they recommended setting the IO scheduler to noop for SSDs. Is that the > case for Cassandra as well, or is it recommended to keep the default > 'deadline' scheduler for Cassandra? > In general the noop IO scheduler is the best suitable one for virtual machines (regardless of C* or SSDs). Usually the hypervisor below or the target SAN/NAS run their own IO scheduler so there is no need to do that twice. >From my own experience (managing the Xen and KVM dev teams @redhat) both deadline and noop gave similar results and were better than CFQ's. > > Thanks. >
