• Resolved Fhoke

    (@fhoke)


    We’re running a site with Yoast installed, the site has 1,177 pages (I know, quite a few!) and it appears Yoast is hammering the memory usage on the site.

    Having Yoast installed is causing the memory allocation to go up from 56MB to 312MB.

    Is there any reason Yoast would be taking up so much memory? I know there are a lot of page, but that seems excessive.

    It’s also worth noting I’m only trying to view the page with 20 posts per page, not anything crazy like 100.

    Thanks,
    Seb.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Suwash

    (@suascat_wp)

    Hi @fhoke,

    We understand you’re coming across with memory issues after activating the Yoast SEO plugin.

    Let’s check a couple of basic things:

    1. Are you using Yoast SEO version 14.9?
    2. Are you using WordPress version 5.5.1?
    3. Are all your other plugins up-to-date?
    4. Does your site meet our plugin requirements?

    We look forward to your response.

    Plugin Support Maybellyne

    (@maybellyne)

    Hello @fhoke,

    Thanks for reaching out!

    Can you please confirm if your website meets the plugin requirements? This guide explains more: https://kb.yoast.com/kb/plugin-requirements/.

    Can you share some additional information like any PHP errors related to Yoast SEO in the server error logs?

    Thread Starter Fhoke

    (@fhoke)

    Hi both!

    Thanks for the speedy reply!

    I can confirm all of the above:

    • Yoast is on version 14.9
    • Site is on WordPress 5.5.1
    • All plugins are up to date.
    • The hosting does meet all of the requirements you’ve listed.

    One thing to note is that the _postmeta table is coming in at 148MB which seems rather large. That being said, out client does have 1,177 pages, all using custom fields, so I guess that could be the cause of that issue.

    Here is a link to the PHP error logs from the last 2 days: https://www.dropbox.com/s/48zme7qkk1l9tpl/20200923040409_CharlesCameronAssociates_logs.zip?dl=0

    Plugin Support devnihil

    (@devnihil)

    @fhoke Thanks for your reply and confirming those details.

    Regarding the issue, does the issue resolve if you try disabling the Yoast related columns in Screen Options for the all pages view? (see image here)

    Also, we do know Yoast taps into the WordPress API to make calls., on some server configurations this may result in unexpected behavior. If you were to go to SEO>General>Dashboard>Features and disable the Text Link Counter, does that resolve the issue?

    Thread Starter Fhoke

    (@fhoke)

    Hi @devnihil,

    I’ve just tried disabling Text Link Counter but that didn’t seem to help.

    Unfortunately I can’t disable any screen options as the page is broken so the link doens’t work: https://www.dropbox.com/s/nu852dta5csgc78/Screenshot%202020-09-24%20at%2008.54.52.png?dl=0.

    Hi @fhoke,

    Thank you for this extra information.

    Based on the information you gave about the number of pages from one author, we might believe you are suffering from a bug we are currently investigating. In some cases, we’ve seen this happening and we are currently investigating the scope of this bug. You can see more information here: https://github.com/Yoast/wordpress-seo/issues/16027.

    If you can or have extra information on the setup you have regarding all those pages and metadata, feel free to add information to the Github issue so our QA and development team has more information. Thank you!

    As a temporary workaround, you could downgrade to our 14.8.1 release on the advanced view of our plugin here on www.remarpro.com.

    We hope to have cleared things up for you. We’ll keep on investigating the issue to get this fixed in an upcoming release.

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Yoast is using 256MB memory for the pages list’ is closed to new replies.