0
Good afternoon!
I have two components installed: Music Collection and Content Statistics. I noticed that the xxxxx_content_statistics table has a very large value in the database - 564.8 Mb. Can we do something about this?
In addition, the hoster sent a notification that a significant part of the site's resources were consumed by requests to the database server.
And gives an example: SELECT COUNT(*) FROM xxxxx_muscol_songs WHERE artist_id = 33; where, according to them, 1787 rows are analyzed without using indexes:
+----+-------------+--------------------+------------+------+---------------+------+---------+------+------+----------+-------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+--------------------+------------+------+---------------+------+---------+------+------+----------+-------------+
| 1 | SIMPLE | v0ecf_muscol_songs | NULL | ALL | NULL | NULL | NULL | NULL | 1787 | 10.00 | Using where |
+----+-------------+--------------------+------------+------+---------------+------+---------+------+------+----------+-------------+
We recommend contacting the developer to optimize SQL queries.
Is there anything you can recommend?
I have two components installed: Music Collection and Content Statistics. I noticed that the xxxxx_content_statistics table has a very large value in the database - 564.8 Mb. Can we do something about this?
In addition, the hoster sent a notification that a significant part of the site's resources were consumed by requests to the database server.
And gives an example: SELECT COUNT(*) FROM xxxxx_muscol_songs WHERE artist_id = 33; where, according to them, 1787 rows are analyzed without using indexes:
+----+-------------+--------------------+------------+------+---------------+------+---------+------+------+----------+-------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+--------------------+------------+------+---------------+------+---------+------+------+----------+-------------+
| 1 | SIMPLE | v0ecf_muscol_songs | NULL | ALL | NULL | NULL | NULL | NULL | 1787 | 10.00 | Using where |
+----+-------------+--------------------+------------+------+---------------+------+---------+------+------+----------+-------------+
We recommend contacting the developer to optimize SQL queries.
Is there anything you can recommend?
Attachments:
Responses (7)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
0Hi,
you can make a CronTask:
Delete Stats < nbr months
Andrey Nesterov wrote:
So:
1) xxxx_muscol_statistics can I delete without any problems? Or is the data in this table used on site pages?
2) If I clear xxxx_content_statistics, all statistics on the site will be reset to zero? Or will the total number of pageviews still be shown on the pages?
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »