Title: Performance issues
Last modified: August 24, 2016

---

# Performance issues

 *  Resolved [Stanislav Khromov](https://wordpress.org/support/users/khromov/)
 * (@khromov)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/)
 * Hi,
 * You have set the autoload option to false on all your options, see screenshot:
   
   [https://dl.dropboxusercontent.com/u/2758854/mainwp-problems.png](https://dl.dropboxusercontent.com/u/2758854/mainwp-problems.png)
 * Why is this a problem you might ask? Well, non-autoloaded options required a 
   separate SQL call every time you run get_option(), so each page load looks like
   this:
    [https://dl.dropboxusercontent.com/u/2758854/mainwp-queries.png](https://dl.dropboxusercontent.com/u/2758854/mainwp-queries.png)
 * What you should be doing is using $autoload = true when registering your options,
   that way they are loaded automatically as part of the WP bootstrap process and
   require no further queries when called.
 * I’m not saying the performance impact is huge, but it is causing 8-10 additional
   queries on each **front-end** page load.
 * [https://wordpress.org/plugins/mainwp-child/](https://wordpress.org/plugins/mainwp-child/)

Viewing 7 replies - 1 through 7 (of 7 total)

 *  Plugin Author [mainwp](https://wordpress.org/support/users/mainwp/)
 * (@mainwp)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119051)
 * I’ll send it over to the Dev team to review.
 * We have an update due within 48 hours so if/when they confirm the issue we’ll
   try and get it in that update.
 *  Plugin Author [mainwp](https://wordpress.org/support/users/mainwp/)
 * (@mainwp)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119195)
 * After discussing the issue with the Dev team it was decided to set Autoload off
   since about a year ago it was causing issues with some users on smaller hosting
   packages.
 * It’s always hard to decide what the best approach should be in cases like this.
   We decided to go with no autoload after the performance issues we had previously(
   loading all options all the time).
 * We will enable the autoload property on the options that are always used in our
   next version to speed up the page load as much as possible without affecting 
   the smaller hosts.
 *  Thread Starter [Stanislav Khromov](https://wordpress.org/support/users/khromov/)
 * (@khromov)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119216)
 * >  We will enable the autoload property on the options that are always used
 * That’s all I was asking for. As long as there are no specific MainWP queries 
   when a front-end user views the page, I’m happy. 🙂
 *  Plugin Author [mainwp](https://wordpress.org/support/users/mainwp/)
 * (@mainwp)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119313)
 * This should be addressed in the latest version for you.
 *  Thread Starter [Stanislav Khromov](https://wordpress.org/support/users/khromov/)
 * (@khromov)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119316)
 * Looking much better with 2.0.16! There are still two database calls left on the
   frontend, for the meta keys:
 *     ```
       mainwp_child_server
       mainwp_backupwordpress_ext_enabled
       ```
   
 * Would be great if you could fix those as well. Thanks!
 *  Plugin Author [mainwp](https://wordpress.org/support/users/mainwp/)
 * (@mainwp)
 * [11 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119317)
 * Thanks we are also looking into the Dashboard queries pointed out by ctalkington
   in this GitHub post [https://github.com/mainwp/mainwp/issues/14](https://github.com/mainwp/mainwp/issues/14)
 *  [Elyx](https://wordpress.org/support/users/kokers/)
 * (@kokers)
 * [10 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119431)
 * Hi,
 * I know that this has been set as “resolved” but it still makes 22 queries with
   each refresh – which is a lot. I am not sure if this has been fixed and there
   was even more queries, or it never did went to the live version of plugin. Has
   this been pushed to production?

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Performance issues’ is closed to new replies.

 * ![](https://ps.w.org/mainwp-child/assets/icon-256x256.png?rev=2734948)
 * [MainWP Child - Securely Connects to the MainWP Dashboard to Manage Multiple Sites](https://wordpress.org/plugins/mainwp-child/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mainwp-child/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mainwp-child/)
 * [Active Topics](https://wordpress.org/support/plugin/mainwp-child/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mainwp-child/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mainwp-child/reviews/)

 * 7 replies
 * 3 participants
 * Last reply from: [Elyx](https://wordpress.org/support/users/kokers/)
 * Last activity: [10 years ago](https://wordpress.org/support/topic/performance-issues-10/#post-6119431)
 * Status: resolved