I was reading the following thread about setting up MySQL on unRAID and had a few questions:

 

http://lime-technology.com/forum/index.php?topic=11473.0

 

To optimize load times on each client device throughout the network, what type of drive should I attempt to install the database? 

 

In my current setup, I have 3, 3 TB HDD, so I don't have a cache drive so it appears I'll need to add something.  The setup is pretty powerful though for an unRAID server as it has 8 GB RAM and a dual core intel.

 

Would it make sense to get some sort of small SSD for this purpose?  I haven't read into it all that much so I wasn't sure what the optimal way to do this would be.  My goal is to have the client devices be able to read all of the data and artwork for the database held on the server in a timely manner.  I also read that others have the server hold the thumbnails and artwork and then the client scans the database once instead of downloading from the internet and then stores the data on the drive of the client device.  I'd imagine this would be a fine solution too?

 

Any advice would be appreciated.

 

Thanks.

I would recommend using a cache drive (any will do) so that the array can spin down. Once the database is loaded it should be really fast (even if you use a 5400 rpm cache drive.)

 

Sent from my SGH-I727R using Tapatalk 2

 

 

If you want speed, bump your ram up to the max your mobo supports and get one of these:

 

<http://www.ubergizmo.com/2013/07/samsung-xs1715-ssd/>

 

740000 IOPS

3000MB/s

1.6TB Capacity

 

Use it as cache, or outside the array.  Then checkpoint it to the array each night.

 

;D

I would recommend using a cache drive (any will do) so that the array can spin down. Once the database is loaded it should be really fast (even if you use a 5400 rpm cache drive.)

 

Sent from my SGH-I727R using Tapatalk 2

 

So any standard HDD will work in this application and have very responsive load times?

 

Will getting something like a very small SSD be more effective?

 

If you want speed, bump your ram up to the max your mobo supports and get one of these:

 

<http://www.ubergizmo.com/2013/07/samsung-xs1715-ssd/>

 

740000 IOPS

3000MB/s

1.6TB Capacity

 

Use it as cache, or outside the array.  Then checkpoint it to the array each night.

 

;D

 

Haha, I guess I should've said one that's reasonably priced.

For the same price, which makes more sense?

 

WD Blue 1 TB Desktop Hard Drive

SanDisk 64 GB Solid State Drive with Low Power Consumption

If you go with an SSD make sure it has good garbage collection as unraid doesn't currently support trim.

 

Sent from a phone, sorry for any typos

 

 

If you go with an SSD make sure it has good garbage collection as unraid doesn't currently support trim.

 

Sent from a phone, sorry for any typos

 

I don't know what garbage collection or trim is.

 

With those being two options (32 GB SSD or 1 TB HDD) which one will provide better results as the storage of database information?

And for syncing these thumbnails, it says on the how to:

 

"You can skip this step entirely if you are using XBMC v12 "Frodo". Frodo will automatically take care of thumbnail caching on each client for you and keep them in sync.  Sharing thumbnails and fanart via path substitution can make loading the library significantly slower."

 

So I guess I should allow them to be cached locally and not worry about them all loading from a single location?  If that's the case, I guess there's really no need for a good HD for the purpose of being able to sync libraries and be able to start/stop in different rooms?

Currently one of my servers runs an old 20gb hard drive from an xbox 360 as a cache drive. I only use it for storing the mysql db. However I literally just ordered two 30gb ssd's to use as cache drives for both systems. I can say the performance currently is ok, but I expect switching to a drive with better read speeds will probably help. The one thing I noticed is that the time it takes to do a db clean in xbmc is substantially longer on my machine with the cache drive than it is on the other machine which has the mysql db running on a seagate 7200rpm which is part of the array.

So I'd assume it's safe to say that a smaller SSD will have a noticeable performance edge over a larger standard HDD?

I don't think the size really matters. Its more the speed of the drive. Ssd drives, for the most part, are faster for reading and writing than mechanical drives. So the ssd should provide better performance. If you don't intend on using the cache drive for the cache function and just plan to use it as an app drive then a small ssd that fits your needs is a good way to go in my opinion. I don't use the cache drive for anything but my apps so I like to keep it small to save on cost.

What tutorial did you use to set up MySQL on the unRAID server?

I actually did not use a tutorial. I just went through it on my own. I will say the easiest way I found to create the user for xbmc was with heidisql. I am pretty sure there is a tutorial on here though.

Do you actually need a cache drive to do this?

 

I'm guessing so because my raspberry pi, which I added the advancedsettings.xml file to must not be locating the database becasue it's booting up with no files.

 

I was able to do all of the stuff given by the tutorial here:

 

http://lime-technology.com/forum/index.php?topic=11473.0

 

It doesn't say anything about where the database is operating.  I guess it's right off the flash drive?

 

Very confused :\

You do not need the cache drive to use mysql. However it will operate out of whatever folder you have defined. This generally means that if you did not specify a location on a cache drive then it will create the database in the array. This means that the drive it is on and the parity drive will both be spun up and used whenever you are accessing the database.

 

Also in the link you provided the first thing I will say is that is extremely old and not necessarily correct for xbmc 12.0 and newer. The second thing is assuming you are using UnMenu like it states then it should have allowed you to define a location for the database files. Take a look in your user shares and you should see a mysql share.