Tuning the Terabytes for SUSE Enterprise Storage
One of the chief questions I frequently hear and see is, “How do I tune my SUSE Enterprise Storage cluster?” Well, now I can answer with a link to the SUSE Enterprise Storage Tuning Guide!
This guide is the culmination of efforts I have been working on for more than a year. This all started as an internal wiki where we started capturing tuning information during the first few releases of SUSE Enterprise Storage. As things progressed and more information was scattered around the web and in conference presentations, I started collecting notes and digesting information.
Then, about a year ago, I began work on the Media and Entertainment Solution guide for SUSE Enterprise Storage. This work centered on the use of CephFS during the media creation process. My goal was to build a fairly performant, all-flash, cluster that would provide suitable capacity and performance for the content creation pipeline and capture the information in a public document. During this work, I also decided to produce a couple of IO500 postings, the first being in June of last year for ISC19 and then again in the fall for SC19.
The data from all of these efforts became the basis for the guide. This includes a lot of OS tuning and some key Ceph tunings that impact performance. However, beyond just the tuning, I wanted to try and explain the associated counters that are utilized to determine if a particular tuning could have an impact. In several cases, this required that I go back to developers to better understand the counters to look at and how to document them in a meaningful way. You can find my engineering counterparts listed on the byline for the document along with the incredible editor/documentation specialist that I was privileged to work with.
With this in mind, I hope that what we have produced helps answer some of your tuning questions and proves to be a useful resource. As always, I won’t claim to be perfect, so if you see something missing, or, dare I say, a mistake, please let us know by using the “Report Documentation Bug” link embedded in the HTML versions of the document.
As always, have a lot of fun!