I have a call from a RAM disk manufacturer working with a customer. They found the Windows server was set to 64K blocks, and asked if that was 'good' or 'bad' as they move through the proposal process.
Thoughts: 1) 16K is the largest block UniData supports 2) We do mostly indexed selects and/or direct reads 3) I know we never need 'read ahead', and in my noggin, the 64K is mostly 'read ahead' 4) BUT... We do have some random 128K and 200K items (large invoices) that have to be read from time to time... So... I'm thinking that 16K would be 'ideal' -- that 32K might still be 'good' (for when we're reading through indexes, or occasional full selects) but that 64K is mostly data we're not going to use anyway, and therefore a waste of time. Anyone have 'real world' views on this subject for 'tuning' Windows disk sub-systems to best serve UniData? David W. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
