Complianz triggers extremely many database connections

  • Resolved Kaleu_87

    (@kaleu_87)


    1 year, 1 month ago

    Hello, our host contacted us today because there seem to be problems on our website. There seems to be an extremely high number of database queries. I looked at Query monitor and sure enough, Complianz is leading the table: over 150 database queries at once. There seems to be a problem here. Here is an excerpt. can you tell us if this is normal or if there are problems?

SELECT option_value

FROM iMNke_options

WHERE option_name = 'cmplz_cookietable_version'

LIMIT 1

1.           get_option()        Plugin: complianz-gdpr   1             0,0001

84          SELECT option_value

FROM iMNke_options

WHERE option_name = 'cmplz_cbdb_version'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   1             0,0002

85          SELECT option_value

FROM iMNke_options

WHERE option_name = '_transient_timeout_cmplz_default_banner_id'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   1             0,0002

86          SELECT option_value

FROM iMNke_options

WHERE option_name = '_transient_cmplz_default_banner_id'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   1             0,0001

135        SELECT option_value

FROM iMNke_options

WHERE option_name = 'cmplz-current-version'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   1             0,0001

261        SELECT option_value

FROM iMNke_options

WHERE option_name = '_transient_timeout_complianz_warnings'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   0             0,0001

262        SELECT option_value

FROM iMNke_options

WHERE option_name = '_transient_complianz_warnings'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   0             0,0001

263        SELECT option_value

FROM iMNke_options

WHERE option_name = '_transient_timeout_cmplz_cookies_ignoredfalsenewfalselanguagefalseispersonaldataallismembersonlyfalsehideemptyfalseshowonpolicyalllastupdateddatefalsedeletedfalseisowndomaincookieallist'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   1             0,0002

264        SELECT option_value

FROM iMNke_options

WHERE option_name = '_transient_cmplz_cookies_ignoredfalsenewfalselanguagefalseispersonaldataallismembersonlyfalsehideemptyfalseshowonpolicyalllastupdateddatefalsedeletedfalseisowndomaincookieallist'

LIMIT 1               

1.           get_option()        Plugin: complianz-gdpr   1             0,0004

265        select * from iMNke_cmplz_cookies where 1=1

AND isMembersOnly = FALSE

AND ignored = FALSE and isTranslationFrom = false

AND deleted != true                     

1.           cmplz_cookie_admin->get_cookies()       Plugin: complianz-gdpr   124        0,0009

266        select * from iMNke_cmplz_cookies where ID = '1'                        

1.           CMPLZ_COOKIE->get()    Plugin: complianz-gdpr   1             0,0002

267        select * from iMNke_cmplz_services where ID = '7'                       

1.           CMPLZ_SERVICE->get()  Plugin: complianz-gdpr   1             0,0002

268        select * from iMNke_cmplz_cookies where ID = '3'                        

1.           CMPLZ_COOKIE->get()    Plugin: complianz-gdpr   1             0,0001

269        select * from iMNke_cmplz_services where ID = '9'                       

1.           CMPLZ_SERVICE->get()  Plugin: complianz-gdpr

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Contributor Aert Hulsebos

    (@aahulsebos)

    Hi @kaleu_87,

    Could you disable the cookie scan under settings, and see this helps?

    Settings – Cookies – Disable the automatic cookie scan

    regards Aert

    Thread Starter Kaleu_87

    (@kaleu_87)

    Hey thanks!

    but isn’t the scan only carried out once a month? That can’t explain 150 database calls every day.

    Greetings!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @kaleu_87,

    Thanks for the info. Most of what you see is the result of following a WordPress best practice, and our focus on minimising load on the front-end. By default, WordPress preloads all options in the wp_options table. If this list is very large, this might slow down the site. For that reason, we set all options that are not used on the front-end to preload=false.

    This means that these options will not get preloaded, which is good for the site on the front-end. The consequence is, that these options need to get queried when needed on the back-end, which explains most of the queries you see.

    Additionally, we currently have our 7.0 version in beta, which lowers the number of requests even in the back-end.

    https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/react

    Let me know what you think!

    Thread Starter Kaleu_87

    (@kaleu_87)

    Hey,

    thanks! The real problem are the huge amounts of database connections, which make our host very mad…So its more a backend thing i guess.

    I deactivated the monthly scan, but it didnt change anything. Do you have other ideas? THe problem ist, that our host will limit us, if we dont get a solution for that. And we really like your plugin and dont wand to start again looking for another one.

    Greetings!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @kaleu_87 my explanation is about the database connections. You can try the beta to see if that works better for you.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Please also note that setting WP_DEBUG and/or SCRIPT_DEBUG to true increases the number of requests, because caches will then get refreshed, and upgrades run. For a correct check on requests these should be set to false.

    If I check the current beta, apart from several options that are loaded with preload=false, I see just one get_cookies() request.

    Thread Starter Kaleu_87

    (@kaleu_87)

    Hey, thanks, but both debugs are already disabled. Do you have an idea, when it will change from beta to release? Greetings!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Can’t say yet. It’s currently in beta. We’ll keep it in beta for a while, then release 7.0 in premium. A few weeks after that it will be released in free.

    I’d say at least two months from now.

    If you need it earlier you can install the beta from the link above.

    Thread Starter Kaleu_87

    (@kaleu_87)

    Hey thanks! I would give it a try but with your link i dont find a downloadable zip of 7 beta. Where can i find it? Greetings!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @kaleu_87 in the right top of that page you will see a green button ‘code’. If you click on it you can select ‘download zip’. This is the zip file you can use to install the plugin.

    Best is to follow these steps:

    – download the zip file
    – deactivate the current Complianz plugin
    – Go to “add new” “upload”
    – Select the zip file, install and activate it.

    That’s it!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Complianz triggers extremely many database connections’ is closed to new replies.