• Resolved Carlos

    (@gengeru)


    Hi there,

    Our website is suffering incidents because MySQL takes a long time to attend all requests and many of our users are receiving a timeout response.

    Examining the MySQL tables I have observed that relevanssi_log table has grown inordinately up to 18 times more (90% of the total) than the wp_posts table (which only occupies 1Gb).
    https://prnt.sc/t4w4jo

    Is there a way to shrink the table and optimize? If we cannot fix this, we will have to remove the plugin and stop using it in our new site, which we are migrating to.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mikko Saari

    (@msaari)

    That’s not the Relevanssi index, that’s the search log, and the size of the search log has nothing to do with the size of your posts. Those are unrelated.

    See Settings > Relevanssi > Logs. There’s an option where you can set the number of days Relevanssi keeps logs. Set that to something, say 30, and Relevanssi will automatically trim the log table to something much more manageable.

    Thread Starter Carlos

    (@gengeru)

    Hi, Mikko.

    I want to reopen this topic because I would like things to be clear to users who may suffer issues like me.

    Since the log table grows so fast, is it possible to TRUNCATE it without fear of a bigger problem? Since it’s unrelated, nothing should happen, isn’t it? And this way I could start with a clean table with the new relevanssi settings.

    Thanks again for your help.

    Plugin Author Mikko Saari

    (@msaari)

    No problem whatsoever, TRUNCATE if you want, but the Relevanssi automatic trimming is a better solution in the long run because it automates the log maintenance.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Relevanssi_log has grown a lot’ is closed to new replies.