#Performance affects of upgrading from 9.12.1 to 9.13.1
1 messages · Page 1 of 1 (latest)
We saw lower latency after upgrading from 9.11.1 to 9.13.1 on our A400
I'm not convinced 9.14 is the greatest to go yet, but 9.13.1 did introduce some TSSE changes. If you use FabricPool and read from cold tiers a lot, 9.14.1 does improve cold reads, and 9.15.1 improves upon that.
I actually feel not comfortable about such generalized statement like "performance will get improved if you upgrade ONTAP from A to B". I have heard it before without any clear elaborations on why, then it turned out no improvement. So, I am seeking for written statement (not just by oral claiming) and better include details why it would improve.
By the way, upon my understanding, beginning in 9.10.1 (not 9.13.1), it introduced TSSE.
In general I agree, but there were plenty of ONTAP versions that flat out inproved performance because of some behind-the-scenes work that was not even exposed to the admin. For example the per-aggregate CP, the TopSpin work for cutting RAID/WAFL out of SAN I/O, or the generic improvements behind the san_optimized flag (AFF vs FAS-with-SSDs)
While I understand what you are trying to say, but those specific technologies you mentioned are all prior to 9.12. To focus on OP's question, and as a most recent example to make my point, what in 9.13. can make the performance improvements in general from 9.12.1 to 9.13.1? Particularly for NFS/CIFS environment?
Paul was talking about changes to TSSE: "Temperature-sensitive storage efficiency adds sequential packing of contiguous physical blocks to improve storage efficiency."
But that's not really performance-related but only improves efficiency savings. (Existing data needs to get repacked though.)
Right. TSSE got changed again.
What is the deal with TSSE? We recently upgraded from 9.8 to 9.12 (and are working on 9.13 currently). TSSE seems to be turned on for some volumes on all AFF clusters, and not others, but we never turned it on. Apparently it is supposed to be enabled by default for new volumes on AFFs, but that is not the behavior I've seen when creating new volumes. So, how did this get turned on for the existing volumes? And, should we turn it on for everything? Apparently, once it's turned on, it can't be turned off again.
Jim I'd open a case. I have no idea.
with the next-gen hardware that just came out, TSSE will also not be a thing anymore anyways 🤷♂️