• Resolved daanilb

    (@daanilb)


    Buenas,

    Desde hace días veo que mi web va muy lenta y tengo problemas con el servidor. Me pongo en contacto con ellos y me dicen que tengo muchísimas tablas en mi base de datos y me pegan estos mensajes.

    1. Executed 51m 56s ago for 67.684362 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 67.684362 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000219 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:25’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    2. Executed 51m 56s ago for 65.070444 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 65.070444 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000171 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:28’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    3. Executed 51m 56s ago for 62.828523 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 62.828523 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000115 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:30’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    4. Executed 51m 56s ago for 62.288731 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 62.288731 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000146 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:30’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    5. Executed 51m 56s ago for 61.127889 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 61.127889 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000111 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:32’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    6. Executed 51m 56s ago for 59.393014 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 59.393014 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000336 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:33’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    7. Executed 51m 56s ago for 59.089263 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 59.089263 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000219 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:34’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    8. Executed 51m 56s ago for 57.287879 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 57.287879 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000269 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:35’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    9. Executed 51m 56s ago for 57.118332 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 57.118332 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000275 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:36’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;
    ——————————————————————————————————————-
    10. Executed 51m 56s ago for 52.288573 sec on Database –> db60ynvuxeuyxo
    Date: 2022-06-05 20:51:33 Query_time: 52.288573 Rows_examined: 4402436: Rows_sent 100 Lock_time: 0.000352 Query_chars: 415
    SELECT p.ID AS ‘id’, p.post_title AS ‘title’, p.post_date AS ‘date’, p.post_author AS ‘uid’, SUM(v.pageviews) AS ‘pageviews’ FROM zeo_popularpostssummary v LEFT JOIN zeo_posts p ON v.postid = p.ID WHERE 1 = 1 AND p.post_type = ‘post’ AND v.view_datetime > DATE_SUB(‘2022-06-05 22:50:40’, INTERVAL 1 MONTH) AND p.post_password = ” AND p.post_status = ‘publish’ GROUP BY v.postid ORDER BY pageviews DESC LIMIT 100;

    Me dicen que tengo como 4 millones de tablas en zeo_popularpostssummary, que me dicen que esto de vuestro plugin. ?Hay alguna manera de no tener tantos datos guardados?

    Gracias.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Hector Cabrera

    (@hcabrera)

    Hola @daanilb,

    Sip, puedes configurar el plugin para que limite la cantidad de data que guarda en la base de datos de tu sitio web: Data Logging.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    @daanilb I have removed your review. Please do not use the review section for support.

    Thread Starter daanilb

    (@daanilb)

    Genial.

    Hector, habría manera para borrar los 4 millones de tablas que tengo creadas?

    Gracias.

    Plugin Author Hector Cabrera

    (@hcabrera)

    Si quieres borrar toda la data de la tabla _popularpostssummary puedes hacerlo utilizando el botón Empty Cache en Ajustes > WordPress Popular Posts > Herramientas, lo encontrarás al final de la página.

    Screenshot of the Empty Cache button

    Ten en cuenta que esta tabla guarda la data de tus posts más vistos en las últimas 24 horas, 7 días, 30 días, etc. Al borrar sus datos tu lista de entradas populares estará vacía mientras la tabla se va llenando nuevamente con datos.

    Para prevenir que suceda el mismo mismo problema en el futuro y si tu sitio web es de alto tráfico (que por lo que comentas parece ser el caso) te sugiero que configures WPP para que limite la data que guarda en tu base de datos (ver comentario anterior más arriba).

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Base de datos enorme’ is closed to new replies.