2 Answers
- Newest
- Most votes
- Most comments
0
Hi Julian,
in case QUIC from inside the container is slow it seems the network stack of the container environment is causing this slowness. Can you try DCV outside of the container to verify it working faster?
Best regards, Karsten
answered 10 months ago
0
Hello,
I understand you are getting not so good streaming quality on QUIC run from container.
Can you try limiting the maximum used bandwidth with using the below methods and see if you are getting better quality:
On Windows:
- Go to registry key: HKEY_USERS/S-1-5-18/Software/GSettings/com/nicesoftware/dcv/connectivity/
- Create a new QWORD: max-target-bitrate
- Set it to 20000 if you need maximum 20 Mbps (set another value, if 20 Mbps doesn't apply to your needs)
On Linux / MacOS:
- Open /etc/dcv/dcv.conf with your preferred text editor
- In the [connectivity] section, do the following:
[connectivity]
max-target-bitrate=20000
The above sets the value to maximum 20 Mbps (set another value, if 20 Mbps doesn't apply to your needs).
On Windows:
> dcvviewer.exe [...] --enabled-quic-alpn-versions="Dcv20Basic"
On Linux / MacOS
$ ./dcvviewer [...] --dqt-alpn-versions="Dcv20Basic"
answered 9 months ago
Relevant content
- asked 2 years ago
- asked 3 years ago
- Accepted Answerasked 2 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
That's difficult, as the container has a lot of libraries for the application to work. Unfortunately, we also found that the Web Client SDK does not support Quic anyway, so my original question is kind of obsolete, as this is a requirement for us.