5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Hi there. I've been trying to understand compression. Looking on NutanixBible, I can read this about inline compression. No impact to random I/O, helps increase storage tier utilization. Benefits large or sequential I/O performance by reducing data to replicate and read from disk. However, when looking at the [video]https://www.youtube.com/watch?v=ERDqOCzDcQY[/video], it seems that inline compression for random I/Os has an impact. 1st of all, it needs to coalesc data before to compress. Therefore, in case of read of any chunk into the coalesced bloc, it will have to decompress all of it. So I guess this is true for any write, and any change in records of a database right ? In that case, Inline compression should only be used for dump databases where data are written once/never read ?! Are there any comparison benchmarks about real (and not feel) performance impact ? I can't say to a customer "use compression, it doesn't feel worse" ... ;-)
Finally a clear answer on the topic :) Now I understand why we can't find any details about it. There are none :)
Well, can be done that way too :) I have to say I don't really understand the purpose of the Backup option, except perhaps to prevent an admin to restart machines we do not want to see running on the DR. Subsidiary question: Does the port 22 need to be open between sites or only 2009 and 2020 ? That's something I couldn't get confirmed in the documentation.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
