Darlis is right. MyDefrag does not read from the disk by itself, and therefore does not have any buffer. Zero. Nothing. The actual moving of data is done somewhere deep inside Windows. I have no idea what buffer size Windows is using.
Thanks Darlis and jeroen! "Buffer" might have been the best word to describe what I was trying to get at. It sounds like you two addressed it exactly. It is too bad MyDefrag doesn't use a buffer as I still can't help but think defrag operations would go so much faster with one. All up to Windows' defrag API though it sounds like.
Then again, there are probably good reasons not to try to implement a buffer in MyDefrag - or perhaps there just hasn't been time to implement it yet? I know with some disc-burning applications you can set a buffer size (beyond the typical 2 MB hardware buffer), though I wonder if the application in that case operates on a "lower" level (closer to hardware) than MyDefrag does and that's why it can do this.
Does anyone know if a read/write buffer is being considered as a future feature? I really wonder if the potential for speed improvement is as great as I'm thinking. From what little I know, it seems like it could even be revolutionary if no one else does it currently - opening up whole new possibilities for algorithms etc.
Thanks again - glad you two understood me haha.