Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested parameters for low redundancy? #331

Open
lars18th opened this issue Oct 1, 2024 · 1 comment
Open

Suggested parameters for low redundancy? #331

lars18th opened this issue Oct 1, 2024 · 1 comment

Comments

@lars18th
Copy link

lars18th commented Oct 1, 2024

Hi,

After reading the wiki for https://github.com/wangyu-/UDPspeeder/wiki/Suggested-parameters and https://github.com/wangyu-/UDPspeeder/wiki/Fine-grained-FEC-Parameters

I still think that the documentation lacks examples for "cases needing low redundancy". For example, you want to stablish a VPN (wireguard) on top of UDPspeeder (with udp2raw). And your WAN connection is realiable with a loss of around 0.1-1% of packets. And no more. Therefore in this case you want that for high traffic not consume more than 5% of redundancy. This will be the case when you are transfering video or doing a FTP transfer. But for other light traffic (SSH/Terminal and/or web browsing) you can increase the redundancy up to 15-20%. However, in any case the total traffic increase will not go over this 20%. The problem is that the "standard" (default) value described in the examples is -f20:10. And this value is far of a 5% of redundancy (in fact is +50%).

Therefore, I request if someone can share values for this use case. And update the wiki with this information.

Any idea? It has sense something like -f4:1,40:1 -i 10 ?
Please share your comments.
Thank you.

@wangyu-
Copy link
Owner

wangyu- commented Oct 1, 2024

Hi, the parameters in Suggested-parameters are just simple example parameters for new users to get started.

I don't provide fine-tuned parameters for very specific use case. If you want to "push the parameters to the limit", you need to do calculation (and experiment) by yourself. Essentially, it's combinatorics math you can calculate by yourself.

But I hear your voice, the current documents are not very clear. So I added a few new documents to the wiki:

https://github.com/wangyu-/UDPspeeder/wiki/mode-0-vs-mode-1
https://github.com/wangyu-/UDPspeeder/wiki/After-FEC-Packet-loss

To "push the parameters to the limit", you will need to do calculation based on your packet-loss and the formular in the 2nd link. Also be aware in real word packet loss is not uniform, you typically need larger redundancy than calculation. Also plz do experiement/verification after calculation, to make sure it indeed works well for you.

By the way, in geranal -f40:1 (or -f4:1,40:1) are not good for default mode (mode 0)( explained in the articles above) .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants