I'm using Transmission 1.04 on Mac OS X 10.5.1.
If I start to download a large file (say 8GB) and then try to quit Transmission, it takes about a minute for it to quit. Activity Monitor says that it's "Not responding" and Transmission constantly writes to disk at a rate of about 30MB/sec. Could somebody explain what it is doing at this time? I don't mind taking a minute to quit (it probably has to disconnect from all peers, stop all threads, etc), but why does it need to write about 1.8GB to disk (60 sec * 30 MB/sec)?
Thanks for any explanation.
Quitting Transmission
Re: Quitting Transmission
Hi there,
I'm bumping this old thread since I'm facing the same problem. I started to download big video files and if I quit or suspend transfers, Transmission stays for long minutes writing at high rate to the disk. This is a problem since if the disk is external (firewire 800), one must wait before disconnecting it. This means that one must anticipate the need to move away with its macBook or else get stuck for minutes (could be very long)
What is curious it that I made a test on the same transfers, using µTorrent. The behavior is identical. So I wonder if it's a side effect of a system call in such case. Activity monitor shows the kernel task heavily processing in the meantime. Definitely not a normal situation.
Edit: Transmission 2.04 - OS X 10.6.4
I found other thread stating that this is only on first quit to allocate the file without fragmentation. My experiment is that it is not only on first quit/pause. Then I don't think fragmentation should be such a concern on moderne filesystem/disks. Is it?
I'm bumping this old thread since I'm facing the same problem. I started to download big video files and if I quit or suspend transfers, Transmission stays for long minutes writing at high rate to the disk. This is a problem since if the disk is external (firewire 800), one must wait before disconnecting it. This means that one must anticipate the need to move away with its macBook or else get stuck for minutes (could be very long)
What is curious it that I made a test on the same transfers, using µTorrent. The behavior is identical. So I wonder if it's a side effect of a system call in such case. Activity monitor shows the kernel task heavily processing in the meantime. Definitely not a normal situation.
Edit: Transmission 2.04 - OS X 10.6.4
I found other thread stating that this is only on first quit to allocate the file without fragmentation. My experiment is that it is not only on first quit/pause. Then I don't think fragmentation should be such a concern on moderne filesystem/disks. Is it?