Hey.
I have a problem with the database. A lot of requests. In hosting support, it was recommended to check the indexes.

Here is their answer:

The ideal option is to optimize queries and put the correct indexes in the tables to minimize the work with temporary tables and sorting without indexes.
I slightly corrected the MySQL parameters (join_ and sort_buffer_size), but they will not help much when doing such queries in bulk.

For example, the following query simultaneously uses a temporary table and sorting without indexes is performed:

SELECT v. *, V. = g.id WHERE v. public= '1' AND v. status = 'ready' AND (v. permissions<= '10' OR (v.creator = '0' AND v. permissions <= '40')) AND (g.approvals= '0' OR g.approvalsIS NULL) OR (g.approvals= '1' AND (g.ownerid= '0' OR (gm.memberid= '0' AND gm.approved= '1'))) GROUP BY v.id ORDER BY v.created DESC LIMIT 625824, 12;

Call result with explain:

------ + ------------- + ------- + -------- + ----------- ---- + --------- + --------- + ------------------------ + ------- + --------------------------------- +
| id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra |
------ + ------------- + ------- + -------- + ----------- ---- + --------- + --------- + ------------------------ + ------- + --------------------------------- +
| 1 | SIMPLE | v | index | creator | PRIMARY | 4 | NULL | 12977 | Using temporary; Using filesort |
| 1 | SIMPLE | g | eq_ref | PRIMARY | PRIMARY | 4 | startleobase.v.groupid | 1 | Using where |
| 1 | SIMPLE | gm | ref | groupid | groupid | 4 | startleobase.g.id | 31 | Using where |
------ + ------------- + ------- + -------- + ----------- ---- + --------- + --------- + ------------------------ + ------- + --------------------------------- +

If you have a connection with the developer, you should consult about optimizing such requests.

How can I fix a mistake?