#Sizer program not working manual#
Manual Scenarios might come in handly when working with existing heterogeneous configurations.įollowing are some considerations regarding workloads imported from RVtools reports: Recently the Sizer tool added the ability to modify Auto configs without changing them into Manual Mode: Notice the Cost delta vs Optimal ratio….Īlso, in Automatic Mode you can specify a really cool subset of options, most of them self-explanatory: As a rule of thumb, once the workloads are defined you should start with automatic configuration and work your way from there. Manual vs AutoīIG discussion topic among my peers in the past. Once these workloads are profiled accordingly, we need to work with Customer on the definition of vCPU:pCPU ratios, Comp/Dedup/EC enablement, etc. Note: For profiling Oracle workloads you can use the Oracle Automatic Workload Repository (AWR) report (requires additional Oracle Diagnostics Pack licensing) You shoud end up with all workloads categorized in some of the following groups (just a guideline list): The logic behind this is thoroughly explained in the following blog from Josh Odgers:īasically, you can calculate the delta between backups in order to estimate the active working set of the workload. If you are lucky enough you may even get some storage metrics for existing apps in current environments (current I/O access patterns, IOPs, throughput, latencies, etc).Ī simple way to estimate the active working set of any given workload is to take a look at it´s Backup statistics. Pay attention to the different types of applications (cloud native, legacy) and in particular the storage requirements for each.
Taking notes as a madman won´t hurt either. They are the ones that know their applications best, so at this stage we need to open your ears and listen carefully. When defining workloads, it´s almost silly to emphasize that Customer´s input is CRUCIAL.
Let´s dive in on a couple of thing to consider when defining workloads and tweaking Sizer options: What hasn´t changed over the years is the need for profiling the required workloads to the most accurate extent, since the proposed hardware configuration is (obviusly) a direct result of this profiling. These days we are lucky enough to have the Nutanix Sizer tool around, so at least this last part of the puzzle can be easily solved. First, the focus was dead on profiling each workload and requirements as accurately as possible, and from there the challenge was narrowed down to matching the resulting workload with the correspondent Hardware Configuration accordingly. I believe some of them applies to any HCI sizing process (I´ve also worked in more VMware vSAN projects than I can remember, which over time led into some form of HCI schizofrenia).īack in the day when Nutanix Sizer wasn ´t available, Nutanix sizing was performed almost entirely by hand. After having participated in many Nutanix projects over the years, I thought it would be useful to some colleages out there to sum up some of the tips I´ve learned regarding the sizing process of a Nutanix HCI solution.