1.3 ?
Larry,
Unless they've changed something recently, the use of MaxTransfer
appears to be a limiting parameter rather than a performance upgrade parameter.
The reason I say this is that if you don't include that parameter in your
mountlist for the FFS drive, you get no difference in performance (using
diskperf) than if you had it set at a number above 32768. If you set it at a
lower number, (such as 4096), then the diskperf figures are the same for buffer
sizes of 4096, 8192 and 32767.
Getting away from diskperf, and into the real world where program sizes
are easily in the 100K category, I'm not so sure that MaxTransfer would do you
much good there either since the loader seems to be the slow down.
I do suspect that MaxTransfer can eat up memory, at least during disk
i/o, since if you ask for 32K bytes at once…they have to be buffered
somewhere.
Perhaps a balance between the buffers, maxtransfer and priority
parameters could be achieved to maximize performance.
Don