1. Home
  2. Docs
  3. Basics
  4. Plugin performance

Plugin performance

Permalink Manager codebase was optimized to avoid the performance issues. To reduce the number of SQL queries, the plugin saves all the custom permalinks in a single serialized array. The main reason for this is that the operations on arrays are generally quicker if they are made directly via PHP.

The plugin works perfectly fine with small and medium sized websites and WooCommerce stores. It means that you can use it to rewrite hundreds and even dozens of thousands of custom permalinks without any hassle.

However, there is one potential drawback of this approach. If you would like use it to rewrite more than 60.000-80.000 permalinks you might experience a slight slowdown. Another problem that can arise is a MySQL error (Got packet bigger than “max_allowed_packet” bytes …) generated when the total size of custom permalinks array is bigger than the value of “max_allowed_packet” variable.

Some hosting providers automatically remove the large database records stored in ‘wp_options’ table. For instance WPEngine could erase the custom permalinks array if its size is larger than 1MB (approx. 10.000-15.000 custom permalinks).

In such a situation, the first recommendation would be to simply exclude the content types that do not need to be filtered my plugin (eg. attachments).