Upload speed about webtorrent-hybrid HOT 10 CLOSED

In theory, it should max out the uplink.

from webtorrent-hybrid.

Hi DiegoRBaquero,

But for me its very rarely touches 2 to 3MB/s, in most other case upload speed is less than 100KB/s

hoping for a solution.

from webtorrent-hybrid.

Are you seeding locally (same computer)? in the LAN? Internet?

Can you show me results from http://www.speedtest.net/?

from webtorrent-hybrid.

I am running the above as js in a Debian server.

from webtorrent-hybrid.

@sunilrx This is most likely an issue with your connection, or with your server's disk speed. Can you test your server speed using speedtest.net or https://www.npmjs.com/package/fast-cli ?

from webtorrent-hybrid.

There is no such thing as the maxing connection speed with the webrtc.
The seeding over Webrtc using webtorrent taxes, insane CPU resources and the faster network speed the more CPU it will use. Eventually Nodejs or something is limiting it. It will rarely go over 20 Mbit.

The crazy CPU usage has been issue since day one and still there is no fix and this is the main reason why webtorrent has not become anything big.
Well there is always a hope someone will find a way!

from webtorrent-hybrid.

@brambox Hi,

EDIT: there seems to have a limitation around 2/3Mbit (200-300kb/s) per peer when seeding, no matter if using desktop app or webtorrent-hybrid cli. I also tried this browser to browser and the speed limit was still there. The weird thing is when i try this within my LAN, it does max the uplink.

@feross @DiegoRBaquero any comment about this, what it might be happening here or where to look ?

my fast-cli speed was 500mbps so the issue isn't there.

I will keep testing and commenting.

Thanks for this wonderful piece of software. I really appreciate it guys.

Nicolas

from webtorrent-hybrid.

Did a little more testing today, fired up serveral instances of webtorrent-hybrid seeding the same torrent on the same computer and speed increased dramatically when requesting it from browser. It certainly looks like some kind of limitation now.

from webtorrent-hybrid.

fired up serveral instances of webtorrent-hybrid seeding the same torrent on the same computer and speed increased dramatically when requesting it from browser

I think this is because the wrtc implementation is different from browser implementations -- currently it's following Chrome M81 -- and it's not quite the same quality, much as the maintainers there try. It's really hard to work with libwebrtc.

Perhaps we can try testing another webrtc implementation that has Node.js bindings. Does anyone have suggestions?

from webtorrent-hybrid.

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

from webtorrent-hybrid.