2012-02-02, 02:11
Hi!
I am wondering how big these files get, so please share your details regarding how many files (music/video) you have and how large your databases have become.
In my setup, the content will not be on the machine hosting XBMC. So the content is not the issue, but rather any local database/user data and if this information does not get particularly large, then I would expect XBMC to keep them in memory and render an SSD unnecessary.
However, if the databases do in fact grow large and the implementation is based mainly around disk operations, then the SSD might be an absolute necessity for a snappy response.
I am wondering how big these files get, so please share your details regarding how many files (music/video) you have and how large your databases have become.
In my setup, the content will not be on the machine hosting XBMC. So the content is not the issue, but rather any local database/user data and if this information does not get particularly large, then I would expect XBMC to keep them in memory and render an SSD unnecessary.
However, if the databases do in fact grow large and the implementation is based mainly around disk operations, then the SSD might be an absolute necessity for a snappy response.