Plugin uses too much database query

  • Hi,

    one of my client’s website is performing bad recently. The server even gives “Response timeout’ errors. New Relic shows, that this plugin is using too much database query (insert and delete) and it is affecting server performance badly.

    Can you please check the plugin, if this can be fixed somehow? Or is there any setting to lower the plugin’s load on database?

    It is running on a WooCommerce website, which has 600-1000 visits per day in average.

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Thomas Geiger

    (@duracelltomi)

    Hi,

    Though we are both Hungarians, I will keep this conversation in English to make it useful for other plugin users ??

    Do you have a query log where we could check what insert/delete queries are affecting server performance?

    In general GTM4WP mostly uses select queries – not directly but using standard WP/Woo get methods -, if you see lots of insert/delete queries, that might be because of the usage of WP transients while the weather/geo data option is enabled. So one thing to check is whether you have enabled the weather data/geo data plugin options.

    Thread Starter Surbma

    (@surbma)

    Yes, this was my original intention also with English language. ??

    No query log, but these images may be useful:
    https://downloads.intercomcdn.com/i/o/340531723/ca894e4d02aaf1ccb5c41560/image.png
    https://downloads.intercomcdn.com/i/o/340531780/fc8549bffd6d399fe12f60b9/image.png

    So one thing to check is whether you have enabled the weather data/geo data plugin options.

    Geo data was enabled. I just disabled this option. We will see, if this makes it better.

    Plugin Author Thomas Geiger

    (@duracelltomi)

    delete_option is only called in uninstall.php:

    https://github.com/duracelltomi/gtm4wp/search?q=delete_option&type=

    Are you sure this is related to GTM4WP?

    Thread Starter Surbma

    (@surbma)

    I’m not sure, the analytics is coming from Kinsta’s support. What I see on the image, I just sent, that one of the longest request is somehow connected to geo data, getting the transient.

    We will see if the disabled geo data may be enough to solve this performance issue or we will disable the plugin temporary to check the website.

    When we know more, I will let you know.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin uses too much database query’ is closed to new replies.