Slowing the plugins index

  • Resolved 18TommyBoy

    (@18tommyboy)


    6 months, 2 weeks ago

    Hello, I have 4 core VPS, WordPress page on it with table “xhc_postmeta (3 429 412 rows, approximately)”.
    With your plugin at start get faster WP site. Few days started super slow and Loadtimes on server 4-6.0…

    ChatGPT helps and we create in SQL a:
    ALTER TABLE xhc_postmeta ADD INDEX meta_key_value_num (meta_key(191), meta_value(20));

    And the VPS load is going down to 1.75 at work. Perfect. But your plugin yet show this:
    https://snipboard.io/UMZTHn.jpg

    Can update the plugin to not asking convert the good keys?

Viewing 1 replies (of 1 total)
  • Plugin Author OllieJones

    (@olliejones)

    6 months, 2 weeks ago

    It would help me understand your situation better if you uploaded your metadata and a monitor. Please read the pinned topic at the top of this forum.

    You can prevent this plugin from pestering you about an index you created yourself by prefixing the index name with index_wp_mysql_protect_.

    If you’re using InnoDB as your storage engine (you probably are) I fear your LLM gave you bad advice. You should not use a prefix index if you don’t have to. Use this index with this name.

    ALTER TABLE xhc_postmeta ADD INDEX index_wp_mysql_protect_meta_key_value_num 
           (meta_key, meta_value(20));

    without the (191) prefix is superior in every way to the prefixed version your LLM suggested. The prefix only exists because of an oddball side-effect of MySQL’s switch to utfmb4. Please read this.

    • This reply was modified 6 months, 2 weeks ago by OllieJones. Reason: Added protection prefix
Viewing 1 replies (of 1 total)

The topic ‘Slowing the plugins index’ is closed to new replies.