Why is Updraft changing PHP memory_limit for all reqests?

  • Why is Updraft setting PHP’s memory_limit to 192 if it is lower?
    It’s doing it in all requests (plugins/updraftplus/updraftplus.php file), not just when it’s making backups or being used by the user.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author David Anderson

    (@davidanderson)

    That code is not run for all requests – see further up the file where there is a return;.

    David

    Thread Starter Jānis Elmeris

    (@jaanise)

    The requests I meant was when I open product list, product page, add products to cart, check out. Maybe not all, but many.

    Those returns you probably mean are included in a conditional block that does not execute for me because $_SERVER['USER'] == 'www-data'. Why is there such condition added, that $_SERVER['USER'] must be empty?

    Plugin Author David Anderson

    (@davidanderson)

    Hi Jānis,

    Yes, I see – thank you. I believe when that line was written – many years ago – $_SERVER['USER'] was only likely to be seen if running the process from the CLI in some way. But some cursory examination indicates that this is no longer the case – it is set at least when running under php-fpm.

    I will look into amending this check for our next release.

    N.B. It’s very unusual to want to run WordPress with less than 192MB available memory these days – it doesn’t take many plugins active to use that up, in my experience, anyway.

    David

    Thread Starter Jānis Elmeris

    (@jaanise)

    OK, thanks!
    Yes, maybe we’ll increase it to 192M from 128M.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Why is Updraft changing PHP memory_limit for all reqests?’ is closed to new replies.