5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Hello Algon, This is referring to one Nutanix Cluster. Let me know, if you have any more queries. Rohan Great, thanks for getting back to me.
Hi @PYBntnx thanks for the reply.Yes, this is my assumption also, except I’m pretty sure SQL is actually using\touching more then 25% of the physical memory. I can see this from within SQL, so this is where I get confused.
Great, yes I read that too.That’s really useful and thanks for replying so quickly. The wording in the Async guide is a bit misleading.
Great, that makes complete sense and well explained. Thanks for taking the time to answer my queries. I could go on asking more but you’ve certainly answered my initial questions and some. Cheers
Thanks again for taking the time to explain. Ah I see, so essentially the reason the data is sequentially drained is to make reading the data later on a lot faster, because as you said reading sequentially is a lot fast then randomly? Is the data replicated to other nodes before it’s drained? Also, just to confirm, any sequential write operation under 1.5MB in size would still be written to the oplog?
Thanks for helping me to understand this better. It makes sense what you’ve said and matches what I was thinking. I’m still a little unclear about this part though “However, if you think ahead about the read that comes next from the extent store, it will be more efficient since the data had been aligned previously.” I’m still unsure about what the benefit is of coalescing then sequentially draining the incoming writes actually has.
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.
