Windows 11, Tixati 3.42, downloading a large torrent (353 GB) directly to an external USB hard drive.

My internet connection delivers ~25 MB/s, which is more than the drive's sustained write speed. What happens:

1. The disk write queue backs up, Windows reports the drive at 100%+ active time.
2. Tixati has no back-pressure mechanism - it keeps downloading at full speed as if nothing is wrong.
3. Eventually the download speed collapses and Tixati locks up completely: UI frozen, the process cannot be closed normally and has to be killed from Task Manager. On one occasion a write was stuck so hard in the kernel I had to physically unplug the drive to clear it.
4. After killing the process, a force re-check of 353 GB is required, which takes many hours on a slow drive.

Workarounds I'm using now: manual download speed limit set below the drive's write speed, and incomplete piece storage moved to an internal SSD. This helps, but a manual global limit is a poor tool - it wastes bandwidth when the disk keeps up and doesn't protect when it doesn't.

Request: Tixati should monitor its own disk write queue/latency and automatically throttle incoming data when the storage device can't keep up (similar to the "Disk overloaded" handling in other clients), instead of pushing until the I/O thread wedges and the whole client has to be killed.

Try updating to the newest release, v3.44 and see if you still have these problems. The v3.43 release was a major update and many things were fixed and improved.

You can set torrent-specific bandwidth limit that is low enough for the drive. It is always applied, no matter what other, general limits are.

Of course, you might say that you need to download 5 or 10 torrents at once to that drive, and have its write performance balanced automatically between all of them. Than we might say that you live a strange life. But who doesn't?