1 Reply Latest reply: Jul 29, 2016 9:29 AM by rfenton RSS

    Performance policy blocksizes - what does it do exactly?

    jayst Newbie

      I'm reading up on best practices connecting apps to Nimble Arrays and a big topic is Performance Policies.

      I try to understand the impact of the blocksize setting and what it actually does different for each value. I'm having difficulty finding documentation about the value, other than recommended values in documents like Proper Block Alignment.pdf

      It's clear to me performance is impacted when blocksizes are not set optimally, but i dont know why   Traditionally back in the RAID configuration era , we've been tuning stripesizes (for full stripe writes), element sizes etc etc, then i knew why, now not so much.

       

      So my questions:

      1.) what does the array actually does different when setting blocksize to 4K instead of 16K?

      2.) Does blocksize have any impact on Compression efficiency? Is a proper blocksize for the used application yield a beter compression rate?

      3.) does blocksize have any impact on Dedupe efficiency for AFA models? Is a proper blocksize for the used application yield a beter dedupe rate?

      4.) does it affect cache ? In what way?

        • Re: Performance policy blocksizes - what does it do exactly?
          rfenton Tracker

          Hi Jayst,

           

          Thanks for creating this thread...

           

          1.) what does the array actually does different when setting blocksize to 4K instead of 16K?

          The goal is to better optimise the application. Everything internal to Nimble is variable block, so it doesn’t affect much on the array operationally other than some fine optimisations internally.

          The tagging of the volume with an appropriate application policy is also very useful for understanding different workloads that are deployed within the install base.  For instance, if we see an obscure application we can use Infosight to understand the attributes of the dataset/application and use that for guidance when sizing and planning for future/other projects.


          2.) Does blocksize have any impact on Compression efficiency? Is a proper blocksize for the used application yield a beter compression rate?

          3.) does blocksize have any impact on Dedupe efficiency for AFA models? Is a proper blocksize for the used application yield a beter dedupe rate?

          4.) does it affect cache ? In what way?

           

          I'll answer all three questions above in one - In short No, the blocksize’s effect on compression, dedupe, cache, etc. would be almost unmeasurable.

          If you'd like a deeper understanding, please feel free to reach out to your local Dutch SE team


          Many thanks

          Rich