This means that the bandwidth of the single cache disk becomes the bottleneck for ALL Tixati's file operations, and to make it worse it is copying all data twice instead of just once, so that bottleneck is exacerbated by the bandwidth being effectively halved. Everything gets routed into a single disk (wherever the cache folder or "Incomplete Piece Storage Location" is located in Settings->Transfers->Locations), and is then copied from that disk out again to the eventual location within the fileset, instead of each piece and file being built in situ directly on the destination disk. Looks like things aren't adding up.Īs I wrote recently in another thread here, the file subsystem of Tixati is extremely inefficient. Interesting to see it is that it reports my torrent to only be 93.8% in progress while in tixati it self it reports 99%. I copied magnetic and then I added my tixati as peer on another torrent client. PS: Looked at my tixati for a torrent that got stuck at 99% i.e. PS: What does Need more blocks to repair mean under the "pieces" tab in properties? I will leave it running over night now as it's already 2AM in the morning. If I can guess, something is stuck in incomplete and then it's hanging. There is about 5 or so peer with this status and yet Tixati doesn't download the last 1%. at the moment.Ĥ7,8GB complete in Remote Peer, 0 remaining, 47,8G totalĥ700 Pieces x 8MB Complete on Remote peer 0 remaining 5700 total Ok so I stopped tixati and it took about 40min for it to finish the shutdown procedure while write incomplete files.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |