Storage of TEXT fields in large volumes in Mysql

Question

MySQL

There is a Mysql server and on it a table of contents of articles.

Structure: id (int), article_id (int), content (text)
About 1.5 million records. The size of the table is 5Gb. The total amount of data on Mysql is 9Gb

Recently, the server has become slower
. Does it make sense to transfer this data to MongoDB to reduce the amount of Mysql data and increase its performance

Answer 1

9GB even for mysql is a small amount. Look for the problem elsewhere. For example, when there was little data, the absence of an index for some more or less frequently used query was imperceptible.

Answer 2

The source data is not entirely clear. In addition to queries, it is also important whether PRIMARY indexes are worth it.
To reduce the disk space occupied with a lightly loaded CPU, you can use on-the-fly text packing using COMPRESS / UNCOMPRESS.

Answer 3

It makes sense sometimes to take out the text field in a separate plate if the data from this table twitches without this field.

Answer 4

It is stupid to store the text of articles in the database - it is more correct to store a link or directly access it by key number. With this approach, you will reduce the load on the database and increase the responsiveness of the server, because you can organize caching at the server and file system levels. For search it is necessary to use Sphinx.
You can minus...

Answer 5

So maybe the base has grown so much that the indexes did not fit into the key_buffer and now the indexes simply stopped using the muscle?