Question about using a SSD as a new content cache.

[avgsmoe 4]

I have recently converted over, and in the process of reworking things I was thinking about adding a 500GB SSD for newly added content, but I was wondering about a few things

 

I am imaging crontab moving the files after 30 days to my main pool.

Would this cause a mess in the library, or maybe, is there a cleaner way to do this?

Secondly, am I wrong in assuming that this would help?

 

 

[Q-Droid 989]

I wouldn't expect much of a gain using SSD to "cache" new media content. If you have typical SATA attached HDD as your primary storage it's more than enough to handle the low transfer rates and sequential nature of streaming.

 

An SSD might help in places like the server cache, metadata cache and maybe transcoding temp files when you have multiple users at the same time. The low latency of SSD could possibly help with UI response for images and metadata when users are navigating. Using SSD for transcoding can do the same, reduce contention for multi-user access.

[avgsmoe 4]

Thanks for the reply. I guess my gadget nature was getting the better of me. The host OS is already on an SSD that should have enough for what you recommended.