this post was submitted on 28 Jul 2023
32 points (82.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54539 readers
278 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

I'm curious to know if anybody else finds their computer behaving sluggishly or erratically when downloading torrents.

For the record: I use transmission on a 2020 imac and have tried other clients to little avial. A virus and/or activity check doesn't reveal anything untoward going on in the background.

I'm not sure what's going on, but torrenting is either resource intensive (possibly RAM) or writing to the harddrive results in poor performance overall. Or maybe its something else (like my vpn draining resources)? Either way, when I torrent I might as well walk away from my computer because that's all it seems it wants to do, and even then its performance remains erratic.

you are viewing a single comment's thread
view the rest of the comments

This depends a lot on the specifics of your torrents, your client, your OS, and your hardware configuration.

In the past I have suffered almost complete system lockups for extended periods because a combination of large torrents, qBittorrent, Windows, and low-speed HDDs caused huge IO locks. I could see in Task Manager that my HDDs were writing at full speed (still higher than my download speed, of course). Even when I had disabled the option to preallocate files, and even if I enabled the option to download sequentially, this still occurred. If you google around you can find similar reports tracing this behavior down to a limitation in libtorrent.

I have never encountered this issue on other OSes, and I'm not sure if this has been fixed; last time I encountered this was probably a couple years ago, and I haven't used Windows much since then.