Hi, I'm having a problem with my qBittorrent setup that I can't quite debug or find information on.

I'm seeding from a hard drive and I get something like 5-15 MBps of seeding capacity depending on the day. However I noticed upon inspecting a system monitor (I am running Debian 13) the total disk IO read was about 4x the seeding speed.

I've tweaked the advanced settings all I can to no avail. I am using the version of QBit from Devian 13 main. It's 5.Something.

Would anyone have insight on this problem? I'll take anything at this point. The application is using about 250MB of RAM.

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

[–] frongt@lemmy.zip 10 points 2 weeks ago (3 children)

Total speed is going to be bottlenecked somewhere, which could be drive read speed, upload bandwidth, or the peer's download speed, their write speed, or any number of other factors.

If your side is capable, don't worry too much about it. You could be seeding to someone on their phone in a shack in remote Mongolia. That's never going to be fast.

Also, reset all the advanced options back to default. You don't need to touch any of them, and changing things might make it worse.

[–] LodeMike@lemmy.today 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Yeah but youd think I would fill some sort kf buffer up eventually, if I'm limited by bandwidth, right?

Am I actually just limited by DiskIO so I'm always behind? My memory usage is around 250MB.

[–] frongt@lemmy.zip 2 points 2 weeks ago

No. There's no point in filling more than the protocol buffers if you can't empty them. Loading a huge file into memory that won't be used right away is a waste.

You've already said your read speeds are better. Memory usage doesn't seem relevant here.

load more comments (1 replies)