The impact of allowing swap

(aabed) #1


I was wondering what is performance impact of enabling the swap on the server running Elasticsearch
Given that the swap disk is on SSD


(David Pilato) #2

You can't really compare direct RAM with SSD drives.
I think that elasticsearch 5.0 might refuse to start in that case because of the bootstrap checks.

(Jason Tedor) #3

Swap on SSD will be faster than swap on spinning disks, but still materially slower than if you just had sufficient RAM. Beyond this general answer, the only way to truly know is to measure (SSD performance varies a lot depending on the disks you have and their configuration), and the only way to know if the performance is tolerable is to have a performance target in mind and to see if your performance measurements enable hitting that target or not. In the end, I suspect you'll just want more RAM. It's cheap, and Elasticsearch will happily leverage the additional room for the filesystem cache.

(Jason Tedor) #4

I'm not sure what you're referring to here? There is a check that if you enable bootstrap.memory_lock then memory locking must succeed (so no silent failing), but otherwise no checks related to swap.

(aabed) #5

Thank you for your reply,
here is the situation

We have a setup where we use a lot of memory and we always adding new machines to the cluster, so someone came up with the idea of adding ssd swap to reduce the cost of spinning more machines

Also what are you referring to as cheap the RAM or the SSD?

(David Pilato) #6

Thanks @jasontedor. I thought we were checking that but was unsure.

(Jason Tedor) #7

RAM for the performance you get out of it. Slow SSDs are cheap, fast SSDs (anything that can push 2 GB/s) are expensive. But even the fastest SSDs are way, way behind RAM speeds.

(system) #8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.