Below you can find instructions on how to install and configure the Scalability Pro Plugin. We are also building a new Scalability Pro support section – any questions asked through our on-site chat relating to Scalability Pro get built into this new support area.
Installation instructions for the Scalability Pro Plugin:
After purchasing the Scalability Pro Plugin, you will receive a zipped file, from there, please follow these steps:
In your WP admin area, click on “Plugins” -> Add new -> Upload Plugin -> Choose file. From there you can select the zipped file you selected and install the Plugin.
There are many options in the settings page, but don’t let that scare you. We are going to go over them one by one and explain what each one does and which one you should use in your case.
Full Text Index Status
A full text index speeds up your search results pages – more impact is gained the larger your site. On our demo site with 817,000 products, the full table scan required to do text search the normal way takes 31 seconds. With the fulltext index, this same search takes 0.2 seconds
A full text index does not yet exist. Adding one will make all your free text search results pages faster.
Note: This may take a LONG time to create if you have a lot of posts – choose a time when you have low traffic levels. e.g. my reference server with 820,000 products takes 20 minutes to create the full text index. Refresh this page to check status and see if it has been created yet.
B-Tree Index Status
B-tree indexes on the correct columns along with some SQL modification speeds up all your archive pages. Archive pages include all your WooCommerce shop pages, your ‘latest posts’ page and your category pages.
Below you can see the indexes created and maintained by this plugin in order to help avoid table scans.
If you suspect table scans are still occurring, follow our guide to identify them: Identify slow queries and table scans
No indexes created yet.
Note: Creating the indexes may time out – refresh this page to view progress and click to create them again if you have to – it will continue from where it left off until all are created.
Enable category/attribute widget SQL cache
|The widget SQL cache caches the complex category/attribute counts based on user filters. If you have your own DB caching, this is not required.|
|Disable WooCommerce widget code|
Remove server-heavy widget-focused actions and filters WooCommerce adds which slow down large sites including get_products_in_view action, wc_change_term_counts filter, layered_nav_init action and price_filter_init action. Choose keep if you intend to use the normal WooCommerce Widgets.
Note: If you experience theme compatibility issues, choosing to KEEP the WooCommerce actions and filters will probably fix them.
Configure WP_Query options:
The following options allow you to optimise WP_Query. You should use the Query Monitor plugin to check first if you have a performance and scalability problem caused by WP_Query. The options are as follows:
This option allows you to use the natural index sort order on wp_posts. When WooCommerce/WordPress/Custom Post Types uses WP_Query to fetch data, it provides sorting options and these sorting options require a full sort of the retrieved data. On /shop/ or large top level categories that means a full table or index scan which can take a few seconds and thrash the disk and CPU.
Note: Using the natural sort order will disable any sort options you currently provide for your users and revert to the natural sort order (normally sort by Date DESC). If you choose this route, you should hide those sort options.
|Calculate totals for current page/search/archive|
When WP_Query fetches posts/products, it also calculates the total number of matching products. This is useful to display at the top of your shop/page, e.g. Showing 1 – 50 of 650,000. However, this count requires either an index scan or table scan. Removing it, can result in ultra-fast WP_Query speed. Depending on your setup, you may need to switch to the natural sort order above too for successful use of the indexes.
Note: Removing count of products/posts breaks normal pagination. You will need to switch to using infinite scroll instead if you choose this option. (there are many plugins which provide infinite scroll and the option below improves all infinite scroll plugins by fixing the back button after visiting product/post detail pages to behave as users would expect)
|Load WooCommerce product pages using Ajax (beta)|
If you use infinite scroll on product archives/post archives, enabling ajax here will make the browser back button come back to original archive page without reloading that page – user will be back at exact product/post position, even if it was on page 2+ and additional server-resource will not be used
To use this option, your CSS must have a 0px margin on the body element or you will end up with 2 scroll bars on the product detail pages.
That should be all, everything written here will be reminded to you on the plugin settings page as well, right under the options. Following these elaborations, you should be able to configure the Scalability Pro according to how you want it and what exactly you need.
In case you are running into issues with the plugin,
please ask a question:Ask a Question