[wp-trac] [WordPress Trac] #49329: memory_limit in site health is not really correct, value is taken from wp_raise_memory_limit

[WordPress Trac]

#49329: memory_limit in site health is not really correct, value is taken from
wp_raise_memory_limit
-------------------------------------------------+-------------------------
 Reporter:  espiat                               |       Owner:
                                                 |  SergeyBiryukov
     Type:  defect (bug)                         |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.5
Component:  Site Health                          |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing 2nd-opinion needs-     |     Focuses:
  patch                                          |  administration
-------------------------------------------------+-------------------------

Comment (by mikeschroder):

 My gut instinct on this is that it's up to the server admin / syseng to
 make sure that the PHP limit is not set higher than the amount of physical
 RAM.

 @zodiac1978 Is this an issue that you've seen trending? I'd be interested
 to find out more about the user concerns to see what the best way to solve
 for it would be.

 A couple notes:
 - On shared systems, hardware memory being available doesn't necessarily
 mean it's available to the individual user or WordPress install/PHP.
 - Memory/RAM may report differently/shift while WordPress is being used if
 it is run across more than one machine (and probably more than one
 instance/container depending on how it's set up or how it's retrieved).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49329#comment:28>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform