Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
Only on the condition that the performance problem is really related to the disk subsystem.
An office disk fully loaded with random requests produces 20 megabytes per second. An SSD of a similar level produces 300.
Well, there will be no extra reading speed, but you still need to be 100% sure that the queries themselves are quite optimal. If you love the asterisk and comma-separated multiple joins, SSD won't save you.
The speed is calculated by the bottleneck, not by the disk system. If you have a small database, most likely it is already cached in the RAM.
Try to conduct tests, determine what exactly you are not satisfied with in speed.
Yes, provided that the database is not entirely in memory.
An access to an ssd disk takes stably 0.1-0.3ms, to a disk - 5-20ms (and the time increases with increasing disk load).
SSD gives a lot more IOPS (operations per second) - 20-150 on hdd versus thousands (or tens of thousands) on ssd.
In practice, of course, it all depends on how often mysql goes to the disk under your load (and indeed on the load).
And yes - reading speed will not give anything, mysql lives well with high IOPS / low latency on the disk.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question