this post was submitted on 06 Nov 2023
183 points (95.5% liked)
Open Source
31185 readers
496 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Torrenting requires way more resources than people realize. It's easy to look at your torrents' download speeds and think "oh, that's less than a normal download, like from Steam, so it must not take nearly as many resources" -- it's not all about bandwidth. The amount of encryption and hashing involved in torrenting is fairly CPU heavy (every ~4 MB piece has to be hashed and verified), especially if your CPU doesn't have onboard encryption hardware (think mobile devices). The sheer number of connections involved even in just one torrent can also bog down a network like you wouldn't believe -- anyone who runs a home seedbox can attest.
For me it's always more.
Same amount of encryption https requires. Hashing is completely optional and is not required for operation, encription is optional too, but other peers may require it.
Which is same. I'm not sure, but steam probably verifies file at some stage too.
There is not difference between 4kpkts for 500 connections vs 4kpkts for 1 connection for network itself. IP and UDP don't even have such concept. Network is stateless. But shitty routers with small conntrack table on the other hand...