Excessive option loading

  • Resolved peter8nss

    (@peter8nss)


    3 months, 1 week ago

    I’m trying to tune my page loading. I notice that on every page I load I get in

    forminator_activated_addons
    forminator_stripe_configuration

    I think this is because these option are not (by default) defined in the options table, so are not autoloaded by wp_load_alloptions, and hence require separate database fetches to check for their existence.

    On other pages, I also seeing individual loads for:

    forminator_addon_campaignmonitor_settings
    forminator_addon_webhook_settings
    forminator_addon_slack_settings
    forminator_addon_mailchimp_settings
    forminator_addon_mailjet_settings
    forminator_addon_aweber_settings
    forminator_addon_googlesheet_settings
    forminator_addon_activecampaign_settings
    forminator_addon_hubspot_settings
    forminator_addon_mailerlite_settings
    forminator_addon_trello_settings

    forminator_paypal_configuration
    forminator_module_enable_load_ajax
    forminator_module_use_donotcachepage
    forminator_custom_upload

    That a lot of unnecessary database calls.

    Could all the addon options be combined as a single option holding an array. That option could be defaulted to an empty array with autoload=yes and a lot of database traffic removed.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Amin – WPMU DEV Support

    (@wpmudev-support2)

    Hello @peter8nss

    I hope you are doing well today.

    Can you please share some more information about how you be able to find these queries, are you using the query monitor plugin to review the database queries (it would much appreciated if you could share some screenshots)?

    In general, forminator codes shouldn’t run on pages where its not used, the mentioned queries only should run on a page where the forminator is used, I checked the running queries in my lab site on different pages but the only query I found was for “count_non_empty_ip_address” its running on most of the page even if the form is not added however it shouldn’t have a major impact on site performance.

    I can see you already reported this issue, a few days ago my colleague brought the issue to our developer’s attention but we need more info about how it can be replicated.

    Best Regards,
    Amin

    Thread Starter peter8nss

    (@peter8nss)

    Yes I am using Query Monitor plugin to find these.

    The first two both arise from the plugins_loaded hook so will be triggered just because Forminator is one of the plugins even when loading pages it isn’t used on.

    The trace back for forminator_activated_addons option is:

    1. get_option()
      wp-includes/option.php:197
    2. Forminator_Integration_Loader->__construct()
      wp-content/plugins/forminator/library/class-integration-loader.php:130
    3. Forminator_Integration_Loader::get_instance()
      wp-content/plugins/forminator/library/class-integration-loader.php:52
    4. Forminator->init_addons()
      wp-content/plugins/forminator/forminator.php:310
    5. Forminator->__construct()
      wp-content/plugins/forminator/forminator.php:104
    6. Forminator::get_instance()
      wp-content/plugins/forminator/forminator.php:85
    7. forminator()
      wp-content/plugins/forminator/forminator.php:509
    8. do_action('plugins_loaded')
      wp-includes/plugin.php:517

    In may be worth checking your database to see whether these options are present in your test configuration database – perhaps because you have some add-ons. If they are in the database, then I assume they are autoloaded, and hence you won’t see an individual call to get_option using query monitor.

    Plugin Support Nebu John – WPMU DEV Support

    (@wpmudevsupport14)

    Hi @peter8nss,

    Thank you for further clarification.

    However, I was still unable to replicate what you have mentioned. I was only able to notice the mentioned queries run on a page where the Forminator is used. I also checked the database to verify if they are autoloaded and confirmed that only the ones that are in use are autoloaded.

    Could you please share a screenshot of the Query Monitor results from your end so that we can investigate this further?

    Kind Regards,
    Nebu John

    Thread Starter peter8nss

    (@peter8nss)

    I was worried that the problem might be specific to my configuration, so I went to a new site I’m developing that didn’t have Forminator installed and minimal other plugins. I installed Forminator and went to the site’s home page. Same result!

    Hello?@peter8nss,

    I hope things are going great for you. I appreciate you for sharing the detailed information.

    I can replicate the same thing on my test site, and for the improvement, we have reported internally to the Forminator team.

    The team will check the request soon and consider an improvement in future updates. At the moment, We can’t share any ETA or can’t make any promise when the request will be improved.

    I greatly appreciate your patience and understanding in this case.

    –
    Thanks & Kind Regards
    Imran Khan

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @peter8nss,

    Please do note that we have raised this as an improvement with our Forminator team so that we can check the possibility of implementing this down the roadmap.

    While we cannot provide a specific timeline yet, you can get updates on our upcoming feature by subscribing to our roadmap at:

     https://wpmudev.com/roadmap/

    Since this feature request has been acknowledged, we’re marking this as resolved for now. However, if you have any queries, please don’t hesitate to ask. Thank you for your understanding.

    Best Regards,

    Nithin

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.