Dispute it, we must...
JonTate 110000B0RP Visits (8281)
“To err is human; to forgive, divine.” Alexander Pope.
Well we are mixing up poetry and Star Wars here today (or tomorrow, if it is already tomorrow where you are), and finish it off with a cryptic message.
Anyway, let's cut to the chase here: a long time ago, in an IBM Redbook far, far away (December 2011), in an effort to get out timely information to the field, the first draft (which was a pre-review version), of the IBM Redbook Implementing the IBM Storwize V7000 V6.3, SG24-7938-01, contained the following statement in error:
All 'fine-grained' implementations, like Thin Provisioning, require the recording of metadata to provide the virtual to physical mapping. At some point this metadata may have to be read or written, and so additional I/O may be required. This is the same for any vendor’s implementation.
Without thin provisioning, SVC code 4.2: 272,505.19 SPC-1 IOPS - See: http
With thin provisioning, SVC code 4.3: 274,997.58 SPC-1 IOPS - See:: http
So why do we mention this? Well apparently, there is some FUD being spread around by one of our competitors that has latched on to our errata that we are more than happy to correct, well, corrected almost two years ago now !
It's a bit of a sauce really, as we say in the UK.