Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upIs there some reason as to why loading torrent from info hash/magnet uri is slower on the web than webtorrent desktop client? #1554
Labels
Comments
joshuajazleung
changed the title
This comment has been minimized.
This comment has been minimized.
|
Guessing webrtc's nat hole bunching takes up most of time... The web don't have a DHT either |
This comment has been minimized.
This comment has been minimized.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This comment has been minimized.
This comment has been minimized.
|
There are simply more peers available to the desktop app. Desktop apps can connect to WebRTC and TCP peers, while the browser can only connect to WebRTC peers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of WebTorrent?
v0.102.4
What operating system and Node.js version?
MacOS, node v10
What browser and version? (if using WebTorrent in the browser)
Chrome 70
Some of my users mention that it takes a long time to load the torrent, some can't load at all. When I tested it, web torrent desktop client does load faster, like in 1-2 seconds, while the my website sometime takes 4-5 seconds to load. Is there some reason for that?