Perfect solution for large database

  • This is an excellent plugin. @olliejones, thank you for contributing this valuable resource to the community.

    We drew inspiration from this plugin and developed a custom solution by incorporating elements from it.

    I have a minor suggestion: while this plugin is powerful, it should be implemented with care. Adding a brief note advising users to test the plugin in a DEV/TEST environment before deploying it in production could help prevent potential issues like crashes. However, we did not encounter any problems, and everything worked smoothly.

    Lastly, a quick question for @olliejones: Are there specific reasons why WordPress does not include such optimized index keys within its core?

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

  • You will want to start from https://github.com/WordPress/performance/issues/132 and a couple of links spreading out from there.

    tl;dr Back-compat concerns, as always, blocking progress. Everyone on modern software stack needs to make their own table stakes performance upgrades, still, unfortunately.

    Plugin Author OllieJones

    (@olliejones)

    Thanks for the kind words. Yes, Leho has it right about backward compatibility. A mess, it is.

    As far as the need to try this in staging goes, I have only heard of a few failures. They have been related to one or the other of these things:

    1. /tmp/ being too small to handle a re-indexing operation.
    2. A table that has been in production while lacking an appropriate UNIQUE key.

    In both these situations, this plugin’s attempted operation and failure left the table unchanged and working correctly. That’s why I don’t specifically suggest trying it in staging.

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