It doesn't match my iperf tests to the same server, either (tested in both directions)
:
Something is wrong with the Channels-DVR test.
:
Something is wrong with the Channels-DVR test.
I have two servers. One running proxmox and another running directly on synology nas. The server running on proxmox gives me 940 up and down. However on my synology nas I get 68 down and 940 up. I used a usb adapter and the native 1 gig on the nas and both gave the same response back. So I thought maybe a bad cable. So tried a different one and got the same thing. So I decided to do a speed test between my computer and the nas by uploading and downloading a movie. Speeds are close to 2Gbps or exceeds. So there is something odd with the speed reporting for download on Synology using Channels Speed Test.
Yeah, it has been determined to not work right for qnap either. Maybe it’s the aggregated links throwing it off. Or it could be that Channels app is not using the full bandwidth in both directions, in some cases. I hope its just a reporting issue, but, regardless, I haven't been having any real connection issues.
I have a further comparison using iperf vs channels speed test on the same apple tv. Keep in mind that iperf is the gold standard for network speed testing:
That's a great number for latency (not to mention it's fast too)!
Yes, I have cat6 drops throughout the house. My ATVs are hardwired. And yes, should be fast, it all runs at gigabit. Channels in-app test doesn't report both directions correctly, though.
iPhone on WiFi to Synology NAS that runs Channels DVR
iPhone using iPerfman v1.3.4 iOS app
Synology docker container running networkstatic/iperf3:latest
@eric @tmm1
Not sure if this old topic is related, but I see a large spike in Channels DVR CPU usage (80-97%) on my Synology NAS when running the new speedtest from my iPhone, just like I did in this old topic using my iPad where Aman fixed something.
As a comparison, iPerf test CPU usage is barely noticeable.
1 Like
Thats probably it. Whatever method cdvr is using to generate and send all those bits is maxing out the cpu before the full available bandwidth is reached.
Seeing these screenshots, I am curious about the units displayed. It looks like latency is being shown with “us” (as in the first-person plural pronoun), rather than “μs” (prefixed with the Greek letter mu for “micro-”). Am I correct?