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

Local UDP packet drops reported in /proc/net/udp #89

Closed
dholroyd opened this issue Apr 4, 2021 · 4 comments
Closed

Local UDP packet drops reported in /proc/net/udp #89

dholroyd opened this issue Apr 4, 2021 · 4 comments

Comments

@dholroyd
Copy link
Contributor

dholroyd commented Apr 4, 2021

In my testing I've been seeing relatively high rates of UDP packet drops reported via /proc/net/udp. I have the same stream being received on the same machine via RIST instead of SRT, and the socket entries for that process in /proc/net/udp report no drops; I hope this shows that the problem is not down to CPU overload etc on the machine hosting the test.

I've not debugged enough yet to show this is a problem with srt-rs, rather than a problem with my own application code blocking the event loop (for example), but I wondered if this is a known issue?

@russelltg
Copy link
Owner

It is probably a srt-rs issue--this library isn't really ready for production use--probably related to #75. I'll take a look at /proc/net/udp, could be a helpful metric.

@russelltg
Copy link
Owner

For high bandwidth connections, it's necessary to increase receive and transmit buffers on linux:

sudo sysctl -w net.core.rmem_default=8388608
sudo sysctl -w net.core.wmem_default=8388608

This allows me to more reliably stream

@russelltg
Copy link
Owner

Also, hopefully #102 might help with this @robertream

@russelltg
Copy link
Owner

Considering this closed for the time being. Re-open if the issue still exists with those increased buffer sizes

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