Why recommend MyISAM ?

  • Resolved Doobeedoo

    (@doobeedoo)


    4 years, 8 months ago

    Hello,

    Just installed this plugin to try it, got this message :

    YARPP’s “consider titles” and “consider bodies” relatedness criteria require your wp_posts table to use the MyISAM enginefulltext indexing feature. Unfortunately your table seems to be using the InnoDB engine. Because fulltext indexing is not supported by your current table engine, these two options have been disabled.

    To restore these features, please do the following:

    Convert your wp_posts table to MyISAM engine by executing the following SQL code on your MySQL client or terminal:
    ALTER TABLE wp_posts ENGINE = MyISAM;

    A quick Google search shows : InnoDB is better than MyISAM, you should use InnoDB most of time

    Is it because YARPP is obsolete ?

    Thanks for the free plugin anyway
    Kind regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Michael Nelson

    (@mnelson4)

    HI @doobeedoo, ya that’s a bit of old code from before InnoDb added support for fulltext indexes, that we’re poised to remove (actually, if you’re eager, I could send you a link to try the next version, which would be very helpful).

    But actually, from my testing on a localhost site with 1000 posts, I found YARPP’s queries on MyISAM were about 20% faster than InnoDB, so we may continue to recommend MyISAM, but not require it.

    Either way, thanks for reaching out to let us know this is something important to you. And no, YARPP isn’t obsolete, although it did have a major lull for a few years there with the previous owners, and the new owner, Shareaholic, is putting quite a bit of effort into making it up-to-date (we just need to careful with every update with so many existing users.)

    Do you have a test site you could try the version of YARPP that doesn’t require MyISAM? No worries if not.

    Thread Starter Doobeedoo

    (@doobeedoo)

    Hi Michael,

    Thanks for your answer and the informations

    Happy to see that you work on the plugin to update it, thanks for offering this free plugin, that’s great !

    For this time, I had more luck with another related post plugin for the set up, but I’ll try YARPP again in the future

    Plugin Support Michael Nelson

    (@mnelson4)

    Ok no worries. Take care!

    Hi Michael,

    we switched wp_posts to MyISAM only for the reason to use YARPP.
    I read that InnoDB has a better performance an some other advantages compared to MyISAM.

    No i can read in the changelog that InnoDB is supported but 20% slower on your localhost.
    1. Do you know why? Do you work on that performance problem?

    Right now i am not sure to switch back to InnoDB for wp_posts because of all advantages of InnoDB.

    2. When do you notice that 20% in queries. On each page view? On first page view?

    Thanks in advance
    Flo

    Plugin Support Michael Nelson

    (@mnelson4)

    Hi @flofiwp,
    1. I think the 20% difference in time between InnoDB is just a trait of each database engine. You can read up all about the pros and cons of each, but often one is slightly better in some situations over the other. In the case of YARPP’s query, at least on my local computer, MyISAM was slightly faster. But that’s hardly an exhaustive benchmark, and it’s possible my antivirus started to run between tests or whatever else, so it’s not an exact comparison. I would suggest you activate the Query Monitor Plugin and see which is faster on your server.
    2. The 20% difference I noticed was just during the first page view, when the YARPP cache gets set. Subsequent queries don’t use the post table indexes (instead use the faster YARPP cache table.)
    I hope that helps.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Why recommend MyISAM ?’ is closed to new replies.