Reply to thread

Message: [QUOTE="Lee Gillie, post: 6566895"] Ok, the single BIGGEST thing I have found was to open the output disk file with SHARE=NONE. This boosted general performance by a factor of about 5. Additionally, I found fiddling with the buffer size on the open affected performance a lot. I found a 64K buffer was about optimal. Using smaller or larger buffers could affect performance by many as much as 10 fold. It seems to be worth testing. Unfortunately, I'll bet the performance profile may vary from hardware to hardware!?!? Curiously, I could not find any difference in either reliability or speed when specifying the ASYNCH param as TRUE or FALSE. Maybe that is because I am protecting the FileStream BeginWrite calls with VB.NET SYNCLOCK? The subject of the need for thread synchronization of streams is all a bit voodoo to me. I have not seen it discussed in depth anywhere. I am now getting about 22 MBIT / SEC total throughput from the socket to the disk file now. I think I can live with that. Also, I found that by finding the optimal throughput the number of buffers needed dropped from about 250 to 80. The number of buffers I allocate is directly caused by the backlog of pending asynchronous writes to the disk file. - Lee [/QUOTE]