Justin Parisi

So anybody who is using NDVP across platforms would have noticed that things like, well, specifying the size of the volume was inconsistent.

You could specify no unit, and it would produce it in gigabytes.

You could produce, or you could specify a giga or gibby type of unit, so base 10, base 2.

With SolidFire, there was no units.

It was always base 2 gigabytes, gibby.

So what we did was basically standardize all of that, as well as provide the ability to do a default.

So the default default is still one gigabyte, but the administrator can specify that the default, if no size is provided, can be something else as well.

So I'm going to dumb it down a little bit.

Correct.

Yeah, so most of the time, we as consumers, right, and I'm lumping us as storage administrators and NetApp employees who are hopefully knowledgeable about this already, but anybody who isn't, right, when you go to the store, when you go online and order a laptop or anything like that, maybe you're going to buy a hard drive that is one terabyte in size, right, one trillion bytes.

However, when you actually go to use that drive, it's going to be something like 930 gigabytes of usable space.

This is because computers operate in base 2 binary.

Marketing operates in base 10.

Exactly.

Marketing operates in base 10 because it's a bigger number.

It is.

I get more for less or less for more.

So effectively, we standardize the units.

The default is now to use the base 2.

So if you're using Docker volume plugin, you say Docker volume create with a size of 10, you will get 10 usable gigabytes of space.