On 11 Dec 2006, at 23:21, Norman Palardy wrote:
On Dec 11, 2006, at 3:58 PM, Jonathan Johnson wrote:
On Dec 11, 2006, at 4:04 PM, Theodore H. Smith wrote:
Unfortunately, that just tells me 4096, which to be honest, is a
kind of sucky buffer size ;)
It's one page, which sounds like a pretty good size to avoid
hitting multiple page boundaries :)
And could probably b read and written in multiples of that size
quite well too
I think I have a good simple answer.
Just make a self-testing function :) I can make it as an RB module,
no need to code it in C.
The module will make some streams and read and write a lot, then
figure out the fastest block size.
Should take out the guesswork. I'd make it as an extends, so
something like this could be done.
ElfDataStream.DetectFastestBlockSize 10 // means the test is run for
10 seconds.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
