<p>I'm creating a Cassandra cluster in Google Cloud Platform in Kubernetes.</p>

<p>I saw that google provides different type of disks, the question is: "Is 'google Kubernetes standard disks' quickly enough for Cassandra?", or I should to change to SSD disks?</p>

<p>I think that the best solution is Local SSD disks, but I don't know if is an overkill.</p>

<p>Anyone have experience with this?</p>

<p><a href="https://cloud.google.com/compute/docs/disks/" rel="nofollow noreferrer">https://cloud.google.com/compute/docs/disks/</a></p>

<p><a href="https://i.stack.imgur.com/kYWHv.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/kYWHv.png" alt="enter image description here"></a></p>

<p><a href="https://i.stack.imgur.com/cTJed.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/cTJed.png" alt="enter image description here"></a></p>

<p>According to cassandra's <a href="http://cassandra.apache.org/doc/latest/operating/hardware.html" rel="nofollow noreferrer">documentation</a>, they recommend </p>

<blockquote>
  <p>local ephemeral SSDs</p>
</blockquote>

<p>Though, you won't notice significant performance degradation running on regional/zonal SSD's.</p>

<p>It is more important to allocate  <strong>commitlogs</strong> (<code>commitlog_directory</code>) and <strong>data dictionary</strong> (<code>data_file_directories</code>) to the separate physical drives.   </p>
