Doing some more testing I created a File i/o volume without initialization. Seemed to work ok and the performance was comparable to another volume that I had done with file i/o with initialization, but the not initialized file i/o was created in seconds!
So I'm wondering what the downside is to using uninitialized File i/o volumes as they seem to not cause the huge performance drain when they are initializing. In the knowledgbase it says:
File IO no initialization:
XFS uses first free block for saving the data – no need to use „SEEK” command.
High performance while „random write”, low performance while sequential read.
File IO with initialization:
System must perform a real SEEK in order to read/write the data.
XFS table has to be read and updated. More stable than “not initialized” volume.
Trying to understand what More Stable means. Will my uninitialized File i/o volumes blow up sometime in the future? I would think if that were the case I don't think initialization would not be an option under file i/o but rather mandatory.
Has anyone out there in Open-e forum land used uninitialized file i/o volumes and had problems?? Or not??
Reply With Quote