I have 1000 Mbps internet. When I do a speediest on my AppleTV with a 3rd party speedtest app, I get ~700 Mbps down and ~800 Mbps up.
When I do a speedtest in Infuse on the AppleTV with my iMac share, I get ~85 Mbps.
Everything is connected with ethernet, so wifi performance is not a concern. Why is SMB so slow?
Are there faster protocols? For example there is this recent thread SMB Performance which seems to state that WebDAV is faster. But I don’t understand how to setup a WebDAV share on my Mac, and I don’t find any guide in the Infuse support articles.
SMB is only slow in Infuse. You could try another app on ATV with SMB and it probably would be faster. Switched yesterday to WebDAV and I’m happy with the speed. Still sad that SMB is very slow with Infuse on ATV.
Before you go to the effort to change protocols or other major changes you may want to try using SMB 2 or Legacy in the SMB settings, I average about 300 Mbps with SMB.
Also the speed test in Infuse isn’t an ALL OUT speed test, it’s meant to simulate the speeds necessary to stream a video which will always be slower than the full throttle file transfer speed since there’s overhead that has to be taken into account.
THE MOST IMPORTANT CONCERN isn’t necessarily how fast is your connection but does it provide you with good video?
And as explained in another thread, this isn’t a requirement for most on a LAN.
And as I said, I consistently get 300+Mbps on mine and have yet found a file size it couldn’t play so it’s not ALL SMB connections that have issues. That’s why maybe the OP can solve their problem with a few minor settings instead of starting over with something else.
The implementation is quite okay. It has been much worse in the past few years. It is not the fault of macOS. It’s the implementation of Infuse. Whether I use a Syno, a QNAP or an OMV server, the performance with SBM3 including encryption and signing is really bad. If I use another app on the ATV that supports SMB3, it brings much higher speeds.
You can easily look this up under macOS. I assume that the person dealing with security sets min v3 in the SMB config and enforces signing as well as encryption. Anything else would be foolish. If the SMB server is configured correctly, an app cannot connect if the minimum requirements are not met.