"asynchronous disk I/O" by the dev of libtorrent (the one used by qBT, not the rTorrent one) in 2012: blog.libtorrent.org/2012/10/as

Show thread

This doesn't matter for light usage, but on a big dedicated server and hundreds of torrents, it's another story

Show thread

Transmission seem to use threads, but not has extensively has qBT.

Show thread

I'll see how qBT does over the span of a couple of days, but for now it's much better than everything I used before in terms of performance

Show thread

I only bumped the async i/o threads to 32 (from 10) because I have 32 cores. I uses more RAM (~8 GB) but I have 96 so it's fine...

Show thread

it's much faster, the web UI/API doesn't struggle a bit

Show thread

ok so I moved all my torrents from rTorrent to qBT on my actual seedbox, it's night and day

Show thread

@aspie4K indefinite (I mean until someone decides to change the pricing model I guess but that's not planned afaik :shrug_akko:)

@aspie4K this is in the free tier:
- 75 GB of storage
- 75 GB of cold storage (GLACIER)
- 75 GB egress
- ∞ egress to scaleway services in the same region
- ∞ ingress
- ∞ requests

@aspie4K You can't use two object storage providers at the same time on Mastodon, FYI

@aspie4K (disclaimer: I work at scaleway on object storage)

Show older

Stanislas's choices:

Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!