search for: mevatron

...trying to use this program with our NAS, which hosts a Samba share on the network. However, the performance of the program is staggeringly slow on Window 7, 8.1, and 10. To make the problem easily repeatable, I created a small C++ program to just write 1 million lines to a file: https://github.com/mevatron/nas-write-test Next, I performed a packet capture of the two OS conversations with Wireshark. I found the Linux SMB implementation buffer many hundreds of lines into each write; whereas, Windows decides to immediately flush it's buffer to disk on each line write, which obviously causes tremend...

...h our NAS, which hosts a Samba > share on the network. However, the performance of the program is > staggeringly slow on Window 7, 8.1, and 10. > > To make the problem easily repeatable, I created a small C++ program to > just write 1 million lines to a file: > https://github.com/mevatron/nas-write-test > > Next, I performed a packet capture of the two OS conversations with > Wireshark. I found the Linux SMB implementation buffer many hundreds of > lines into each write; whereas, Windows decides to immediately flush it's > buffer to disk on each line write, which...

> > > Does the wireshark trace show the Windows client asking for and > getting a RWH lease under SMB2 ? If so, then there's no reason > it can't be caching the entire file locally. Seems strange > behaviour from the Windows redirector here. > I have uploaded the Linux packet capture here (14MB): https://drive.google.com/open?id=0B6UHr3GQEkQwWXJ1NjVwMkJXOEU Also,

> The Linux client is asking for SMB1 and using 1MB write sizes. > > The Windows client is using SMB2 and *NOT ASKING FOR LEASES*. > > This is why the performance is terrible. Because the file > as no lease, the Windows redirector must pass every single > WriteFile() system call onto the wire, no matter how small > the size. > > If you can get the Windows SMB2 client