View Single Post
pipeline's Avatar
Posts: 693 | Thanked: 502 times | Joined on Jul 2007
#67
Originally Posted by speculatrix View Post
my guess is that torrent clients thrash their disk files, and will absolutely cause early failure of flash memory, so definitely ensure all files - temporary and final - are not in internal memory.

does os2008 have tmpfs in the kernel, so that you can have a ramdisk backed by a big swap file on external flash, which might reduce the amount of I/O to the cards?
Well i was hoping to hear back from original author but this is my take (guesstimate) on this (having searched their forums) :

If you are saving downloads to mmc card (instead of internal memory) then :
- Transmission only will use internal storage for caching (sha?) hashes (like checksums) and peer information. I would guess the bandwith of 'writes' to internal memory are order of magnitude like 1:100 for the file size your downloading. Probably negligable for all but the heaviest downloaders.
- Transmission currently -does- have ability to relocate the home directory (where cache files are written), but unfortunately that 'branch' is also used for some file types (socket files) which would not be compatible with relocation to fat/fat32 sd/sdhc cards. If you are a hardcore downloader you could set up (ext2?) partition and try relocating home there with environment variable TRANSMISSION_HOME=/media/mmcwhatever (i cant verify this since my cards are current formatted fat32). If you try this just edit the launcher script /usr/bin/transmission and add that TRANSMISSION home assignment before call to executable.

I asked the author for an alternate variable/setting to relocate just the cache, but he has yet to respond. If he does i'll be sure to post info about it here.. although i'll still probably leave the default to cache hash in /home/user/.transmission.