Slow internet speed

With ReadyCloud running and "uploading" and connected locally. Surface in exact same spot, so not sure why signal is 94% versus 99% previously.

There is 1 interface on the system:

Name : Wi-Fi
Description : Marvell AVASTAR Wireless-AC Network Controller
GUID : a4672fee-51c7-45a1-b60d-8188231a8226
Physical address : c4:9d:ed:03:ae:3b
State : connected
SSID : RTK50GHz
BSSID : 7c:d9:5c:02:89:c3
Network type : Infrastructure
Radio type : 802.11ac
Authentication : WPA2-Personal
Cipher : CCMP
Connection mode : Auto Connect
Channel : 149
Receive rate (Mbps) : 81
Transmit rate (Mbps) : 81
Signal : 94%
Profile : RTK50GHz

Hosted network status : Not available

So your wireless connection does certainly allow some 400 Mb/s up and down, while the wired Ethernet does allow 100% reliabe 1000 Mb/s up and down. With the ReadyNAS on the same [W]LAN and the same location (correct?) does flow direct between your Surface and the ReadyNAS - not over the Internet, so it does not take any up-/down- bandwidth from the Internet connection.

However, the wireless (and "Internet" connection) problem does start here:

---

tkernaghan wrote:

With ReadyCloud running and "uploading" and connected locally. Surface in exact same spot, so not sure why signal is 94% versus 99% previously.

 

There is 1 interface on the system:

Name : Wi-Fi
Description : Marvell AVASTAR Wireless-AC Network Controller
...
Receive rate (Mbps) : 81
Transmit rate (Mbps) : 81
Signal : 94%

---

I would not care much about the signal level (or quality). Much more concerning here is the fact that the wireless link PHY speed does drop to 81 Mb/s only - this is certainly a problem. But this is something Microsoft and Google should look into. It does not make any sense that a heavy used wireless link - by a single device (mainly the Surface along probably the single mobile phone) - does fall back.

How the "same" problem appears while using the Gigabit Ethernet connection is (without intense troubleshooting) beyond me. Here again, some throughout should not have such a heavy impact that other connections over the same link and local IP stack. This does move the suspect issue away from the Surface towards the Google Fiber router.

A normal network connection with a usual IP stack does - as there is no QoS or other prioritization - allow to surf the Internet concurrently (or use other network connections on the LAN) while an application like ReadyCloud is making heavy use of the bandwidth.