Log In     Register    

Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

incomplete piece storage - option not use ssd

by Guest on 2025/01/20 03:31:17 PM    
Hi,

Thank you for the wonderful software.

For incomplete piece storage - is it possible to not use SSD or NVME SSD completely? Possible to provide an option to just use RAM so that the life of SSDs will not be impacted?

I understand that if system is crashed, these pieces will be lost, however, if user does not feel any impact of it - user can choose not to write to disk until the complete piece is available.

With Regards
Pavan
by Guest on 2025/01/20 07:05:33 PM    
>>is it possible to not use SSD or NVME SSD completely? Possible to provide an option to just use RAM
Yes of course. Use a RAM disk (ask google how) and configure Tixati to use it - Settings/Transfers/Locations/Incomplete Piece Storage Location.
It is necessary to choose that RAM disk software, which knows how to make its own backup and restore it when the computer is turned off/on.
by Guest on 2025/01/23 03:53:23 PM    
Great!  A new concept knowledge for me.  Let me try.
by Guest on 2025/01/24 05:11:55 AM    
I think I need to explain that Incomplete Piece Storage Location does not mean that each piece of the torrent gets written there. I am not aware of any client that writes data to a temporary disk location just to copy it to the target file immediately, it makes no sense.

This is the place for pieces that belong both to files that are selected for download, and to files that aren't. Because torrent clients can only validate a complete piece, the remaining extra data is kept there. Some other clients save those parts to incomplete target files, which can result in inconveniences with dealing with them, or to a special subdirectory in the target location.

Unless you are unlucky, and have to constantly download random small files from torrents having tens of thousands of them, with much bigger total size and piece size, incomplete-pieces in your client should be negligible in size compared to the total amount of file data written to disk. And you still have to do it each day all day to affect SSD life expectancy. If you really have some server with some fast internet link, you should consider disks as replaceable parts anyway.

If your pieces folder grows constantly, you probably delete files from the file manager instead of deleting them in client, which also removes the extra neighbours.
by notaLamer on 2025/02/02 08:45:59 PM    
I wouldn't bother with a RAM disk, because if you have used Tixati for a long time and many incomplete transfers, it can grow to a gigabyte in side.
The TBW (Total Bytes Written) stat of modern SSDs is high and to be honest shouldn't be a concern. I had tried to preserve my first SSD too, but its cells degraded in speed faster than the TBW statistic. It still sits at like 98-99% health. If you really take this seriously, you should've shrunk your data partition by 5-10% to have spare space for write-leveling. Ideally before you had written any data to disk, but you could zero it manually after shrinking too (low-level writing of all zero bytes to disk area... a process that can go wrong if you miscalculate the from-to position). At the same time TRIM should work too, so it should equate to leaving 10-15% space in a data partition free at all times.

TBW: https://techcommunity.microsoft.com/blog/filecab/understanding-ssd-endurance-drive-writes-per-day-dwpd-terabytes-written-tbw-and-/426024
TRIM aka discard: https://en.wikipedia.org/wiki/Trim_(computing)
by Guest on 2025/02/08 08:03:04 AM    
Meanwhile I wonder if I CAN get tixati to use some kind of tiered caching system.

I have a lot of transfers on old mechanical storage and peak transfer rate for tixati is only 40-50 MB/s on a 1gig connection, simply because of how taxing writing out multiple pieces in random locations on a platter is to a mechanical drive.
It would be kinda cool if it could download pieces to my SSD with speedy random I/O performance, then copy over finished files to the specified download location in a sequential manner.
¯\_(ツ)_/¯
by Guest on 2025/02/09 06:16:47 AM    
Then download to SSD, and move the files on completion to HDD? It's in the settings already.
by Guest on 2025/02/13 03:53:02 PM    
I can of course do things manually.

But it would be cool if we had an automated option. Unfortunately there is no setting like that.

What I want is "Download to X then move to specified location."
What we have is "Download to specified location then move to X."

Specified location = location you choose when starting torrent
X = location you choose in settings




This web site is powered by Super Simple Server