We did. Found that, even with (CentOS, Ubuntu both for application compatibility reasons) that there is somewhat less IO and better CPU throughput at the price point. At the time my optimization work for that client ended, Amazon was looking at the IO issue, as perhaps the frame configurations needed further optimization. this was 2 months ago. A very superficial (no kernel tuning) done last month seems to indicate the same tradeoffs. Testing was performed in both cases with C* stress tool and with CI test suites. Does this help?
*.......* *Daemeon C.M. ReiydelleUSA (+1) 415.501.0198London (+44) (0) 20 8144 9872* On Wed, Mar 1, 2017 at 3:30 AM, Romain Hardouin <romainh...@yahoo.fr> wrote: > Hi all, > > AWS launched i3 instances few days ago*. NVMe SSDs seem very promising! > > Did someone already benchmark an i3 with Cassandra? e.g. i2 vs i3 > If yes, with which OS and kernel version? > Did you make any system tuning for NVMe? e.g. PCIe IRQ? etc. > > We plan to make some benchmarks but Debian is not listed as a supported OS > so we have to upgrade our kernel and see if it works :P > Here is what we have in mind for the time being: > * OS: Debian > * Kernel: v4.9 > * IRQ: try several configurations > Also I would like to compare performances between our Debian AMI and a > standard AWS Linux AMI. > > Thanks! > > [*] https://aws.amazon.com/fr/blogs/aws/now-available-i3- > instances-for-demanding-io-intensive-applications/ > > >
