You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser implementations of of webRTC in chrome/webkit seem to not be able to surpass about ~30-40 MB/s when sending binary data over a dataChannel due to different overheads like IPC serialization, encryption, according to this comment: https://issues.chromium.org/issues/40268944#comment5
I'm imagining this rust implementation not having any of those overheads and generally being fast would be able to well surpass 30 MB/s when transferring binary data over a datachannel, am I correct with this assumption?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Browser implementations of of webRTC in chrome/webkit seem to not be able to surpass about ~30-40 MB/s when sending binary data over a dataChannel due to different overheads like IPC serialization, encryption, according to this comment: https://issues.chromium.org/issues/40268944#comment5
I'm imagining this rust implementation not having any of those overheads and generally being fast would be able to well surpass 30 MB/s when transferring binary data over a datachannel, am I correct with this assumption?
Has anyone done a benchmark or have example code to compare against a browser datachannel speed test like this one? https://lgrahl.de/examples/dc/dc-speedtest.html
Beta Was this translation helpful? Give feedback.
All reactions