V
V
VMConsult2014-01-31 20:42:41
MySQL
VMConsult, 2014-01-31 20:42:41

Hosting MySQL + Sphinx + serving files

It is planned to move to a new server, there will be a good load on the disks. Where is the best place to put the data?
Now the data size is as follows:
MySQL - 60GB
Sphinx - 10GB
Files to return - 100GB (.flv streaming) + cache (a bunch of small 10GB files, constantly overwritten).
In total, two disks are available:
1. 300GB SAS 15k
2. 256 GB SSD
I tend to hang the base and the sphinx on the SSD, and everything else on the SAS. How will it be better?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
A
AxisPod, 2014-01-31
@AxisPod

And how much memory? In general, the files should also be somehow accelerated, this is a moot point, I would push small files onto ssd (how many per day / hour are they constantly overwritten?), An option to keep the cache in RAM. Random access will quickly gobble up all the IOPS from a SAS disk. Again, for a muscle, especially if there is enough memory and InnoDB storage, it can be merged into SAS, it will still keep the base in memory.
Without knowing the specifics, it's still difficult to say, look first of all at the IOPS of disks, and not their speed.

E
Eugene, 2014-01-31
@Nc_Soft

And you have no other options, on sas files for distribution, on an ssd base.

K
klirichek, 2014-04-22
@klirichek

In sphinx, io-load is mainly at index start/rotation. And when searching, the dictionary and attributes are in memory, only spd / spp files are read from the disk (random)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question