• I put 8196M in php.ini as available memory. I’m using PHP 7.0.10 on Centos 7.2 and a dedicated server. This server has 32GB of ram.

    When I try to run WordFence benchmark, I get this:
    Wordfence Memory benchmarking utility version 6.1.15.
    This utility tests if your WordPress host respects the maximum memory configured
    in their php.ini file, or if they are using other methods to limit your access to memory.

    –Starting test–
    Current maximum memory configured in php.ini: 8196M
    Current memory usage: 14.00M
    Setting max memory to 90M.
    Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
    to determine how much memory your host allows. We have requested 90 megabytes.
    <br />
    <b>Fatal error</b>: Allowed memory size of 94371840 bytes exhausted (tried to allocate 67108872 bytes) in <b>/home/vhosts/xyz/wp-content/plugins/wordfence/lib/wordfenceClass.php</b> on line <b>3691</b><br />

    Is it working as expected? It’s as if WordFence or WordPress doesn’t use all the available memory I set. I seldomly get locks from WordFence causing me to have to restart httpd (maybe one every two weeks).

    • This topic was modified 9 years, 7 months ago by keyra.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter keyra

    (@keyra)

    I now use:
    – WordPress 4.6.1
    – PHP 7.0.11
    – WordFence 6.1.17

    I still have a similar error:
    Wordfence Memory benchmarking utility version 6.1.17.
    This utility tests if your WordPress host respects the maximum memory configured
    in their php.ini file, or if they are using other methods to limit your access to memory.

    –Starting test–
    Current maximum memory configured in php.ini: 128M
    Current memory usage: 8.00M
    Setting max memory to 90M.
    Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
    to determine how much memory your host allows. We have requested 90 megabytes.
    <br />
    <b>Fatal error</b>: Allowed memory size of 94371840 bytes exhausted (tried to allocate 67108872 bytes) in <b>/home/vhosts/xyz/wp-content/plugins/wordfence/lib/wordfenceClass.php</b> on line <b>3714</b><br />

    • This reply was modified 9 years, 7 months ago by keyra.
    Thread Starter keyra

    (@keyra)

    I took some time to test it further based on these:
    https://docs.wordfence.com/en/Wordfence_system_requirements#Memory
    https://www.watters.ws/mediawiki/index.php/Test_PHP_memory_limit

    I concluded that this line exceeds the 128MB limit of PHP:
    $a = str_repeat(“0”, 132120545);

    I got this in my log:
    PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 132120577 bytes) in /var/www/html/memtest.php on line 15

    (132120545 + 32 = 132120577)

    I’m still investigating why WordFence (or WordPress) don’t give similar results for available memory.

    I think it may be because it is reserved by WordPress, plugins, themes or WordFence as mentioned in WordFence docs. It’s odd and I don’t fully understand it yet.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Wordfence benchmarking’ is closed to new replies.