Get WPFTS Pro today with 25% discount!

Slow down for bulk operations

Bugs and Fixes
1 1 631 1

  • Hi,

    Overall a great product, but I've found one issue that is affecting us.

    We have a process where we remove large numbers of posts and reimport them from a different system.

    Since the rewrite of the indexing system, if I go to the Posts screen in the admin area, select a pages worth (i.e. 20 of them). Then from the "Bulk Actions" move them to the Bin (Trash), it will take a good 20 seconds to finish the operation. With larger posts it can be a lot longer than that.

    Then going to the Bin and Emptying it, will take even longer. From what I can tell from doing some profiling with xdebug, it's calling curl to do a reindex for every save_post. Which seems fair enough.

    To speed things up, I thought we could uncheck the "Auto-index" box in the WP FullText Search Options screen. But unchecking that and saving, or unchecking the "Enable FullText Search" and saving, it still does the curl request and is noticeably slow.

    If I deactivate the plugin, then normal processing times return and the bulk operations resume at normal sub 1 second speeds.

    This is equally true for importing new posts, or creating them with wp cli.

    My work around for the moment, is to deactivate the plugin before I do any bulk delete/creation operations, then do them, then reactivate the plugin, and go to the control panel, then pause and resume indexing and it seems to catch up (usually quite fast!).

    Would it be possible to put some sort of functionality in, where a save_post call doesn't block it's completion until it's been indexed, or a option put into the control panel where you could allow for it to asynchronously index posts rather than intercepting every single post save?

    Also the unchecking of "Auto-index" option, still seems to leave some of the intercepting of post saving enabled!

    Many thanks.

    Rupert

Suggested Topics

  • No PDF results

    Bugs and Fixes
    2
    0 Votes
    2 Posts
    54 Views
    EpsilonAdminE
    Hi @ultraman Thank you for your message. Since you can see results in the Sandbox, the index is fine. No need to rebuild it again. The problem is on the "display results" side. With your configuration, the first idea I think is to install the pre-release WPFTS version that contains the latest fix of the Divi Addon for WPFTS. I've sent you the link in private messages. Please install it and tell me if it works fine or not. In case it still does not work, please tell me which version of Divi Theme you are using, the WPFTS plugin version, and also please explain your search behaviour. Simple try the request like this: https://yourdomain.com/?s=<search_phrase> And notice if it returns any result. Thank you!
  • How to get Access Level 2?

    Bugs and Fixes bug fix
    11
    0 Votes
    11 Posts
    255 Views
    N
    @EpsilonAdmin I sent you an email. Please check it.
  • No valid search resulds, whats wrong?

    Bugs and Fixes
    10
    1 Votes
    10 Posts
    671 Views
    EpsilonAdminE
    Hi @stark Unfortunately, WPFTS does not work with PODS custom fields "from the box", so custom code exists somewhere. I think your developer used another way to add data to the search index. We need to ask him or alternatively, I could check your code myself, it should not be too long. In this case please send me admin access to your resource using a private message. Thanks.
  • Link URL showing up in search results.

    Bugs and Fixes
    6
    0 Votes
    6 Posts
    448 Views
    EpsilonAdminE
    Hi @jgregory_ca Okay, the fix for Avada addon should be ready in a couple of days. Just FYI. Thanks!
  • Search Results - BOOLEAN Operators and Relevance

    Bugs and Fixes
    2
    1 Votes
    2 Posts
    865 Views
    EpsilonAdminE
    Hi @Nick Yes, the algorithm thinks the number of words here is more important than the exact phrase... Ideally, if we could justify the relative weight for the phrase matches. Currently, it's too low for your case, but I think if we can double it, this could solve the issue. I think to put this parameter to settings in the near future. Thanks!

Be the first to read the news!

We are always improving our products, adding new functions and fixes. Subscribe now to be the first to get the updates and stay informed about our sales! We are not spammy. Seriously.

Join Us Now!

We are a professional IT-team. Many of us have been working in a Web IT field for more than 10 years. Our advanced experience of software development has been employed in the creation of the WordPress FullText Search plugin. All solutions implemented into the plugin have been used for 5 or more years in over 60 different web-projects.

We are looking forward to your comments, requests and suggestions in relation to the current plugin and future updates.

ewm-logo-450

The forum powered by NodeBB | Contributors