Measuring throughput while checking network health
I just wonder why network health feature is only checking round trip time.
On the below screenshot I know I have network issues, the bandwidth is rate limited to 0.7 Mbps, still I get reassuring 'No problem here' answer when checking network health.
IMO, network health depends on more factors than just solely round trip time.
- 最新
- 最多得票
- 最多評論
Hello,
As you might be aware 'Task manager' might not be the best way to calculate the available bandwidth to the client computer. The screenshot shows the amount of bandwidth being used by the workspaces process. The actual bandwidth available to the machine could be higher.
Moving further, here are a few suggestion which you might consider checking to see if it helps:
A) Use High DPI display support. Please refer link[1].
B) Try WSP protocol if not already using it. Please refer link[2].
If you still experience issues post following the above suggestions, we would require details that are non-public information to investigate further. Please open a support case with AWS using the following link: https://console.aws.amazon.com/support/home#/case/create
References:
[1] https://docs.aws.amazon.com/workspaces/latest/userguide/high_dpi_support.html
[2] https://docs.aws.amazon.com/workspaces/latest/adminguide/amazon-workspaces-protocols.html
相關內容
- 已提問 1 年前
AWS 官方已更新 2 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
Thank you for the answer. I cannot agree more, Task Manager is not the most suitable tool to measure the bandwidth available to the client. What I was trying to highlight here is: the tool that could actually measure it is missing the function to do so.
What I'm missing is a test function that sends predefined amount of data to the server and measures the throughput. Something like what speedtest.net is doing. The client can have a very good roundtrip time and a very low available bandwidth (due to an active rule in the client's network for example) which
yet the client reports your network is healthy.