We found the best setting for page size was to match the size of the cluster size of the drive the database was expected to run on
4096 in Win32 machines and 1024 on nix ones (I think, I am no expert on Unix style OS's) I would think, if you set it to the exact size of a number of records all you'll get is the OS ignoring that and loading the chunks of data in the HDD cluster allocation size Clustering the records of your DB will also reduce load times significantly, in that if the records are all near each other on disk, you can get one single READ of a HDD allocated cluster yet retrieve multiple records (if that makes any sense :) ) > I could not find a document explaining how to find the optimal value for the > "page size" parameter. > Should I set the page size to match the allocation size (cluster size) of > the file system ? > Should I set it so that each page contains exactly a given number of records > (i.e. no record is split between two pages) ? > > Thank you, bye >
