Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @18tommyboy, thanks for getting in touch again.

    Wordfence doesn’t use the MEMORY table unless you’re viewing the Login Security settings, so just having that table exist won’t be adding to load times for the homepage.

    It’s fine to change all of the other tables to InnoDB, if that’s the main concern. If tables are originally created while your database is using MyISAM as the default, they would remain that way. We don’t change the engines for any tables automatically.

    Having the main page load faster sometimes seems to point to a page cache serving the homepage rather than any changes made to the database storage engine types. Are you using a database cache? That could cause issues with both Wordfence and action scheduler, and can make a site slow when actions that should happen once are repeated more often.

    Thanks,
    Peter.

    • This reply was modified 11 months, 4 weeks ago by wfpeter. Reason: Clarified the last paragraph about caching
    Thread Starter 18TommyBoy

    (@18tommyboy)

    I have all same settings in LiteSpeed cache plugin (with OpenLiteSpeed server). Only click in aaPanel on Convert all to InnoDB and the site get load…

    Plugin Support wfpeter

    (@wfpeter)

    Okay @18tommyboy, thanks for the information.

    If you still feel there are issues, we will be able to test the site speed ourselves, or see any configuration issues if you send us a diagnostic. You can send it to wftest @ wordfence . com. You can do this directly from the link at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks again,
    Peter.

    Thread Starter 18TommyBoy

    (@18tommyboy)

    I converted the database in aaPanel, yet is good. But when create new site, again this problem. Yet I am okay…

    Plugin Support wfpeter

    (@wfpeter)

    You may need to change the default table engine in your database for new sites, as I notice that mine are already in InnoDB straight from WordPress installation with no conversion necessary.

    Thanks again,
    Peter.

    Thread Starter 18TommyBoy

    (@18tommyboy)

    Default is InnoDB, no problem only when Wordfence is installed. After it must convert again DB.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Not InnoDB, version 2’ is closed to new replies.