[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.1
Component:  Site Health                          |     Version:  5.3.2
 Severity:  normal                               |  Resolution:
 Keywords:  needs-testing 2nd-opinion needs-     |     Focuses:
  patch                                          |  administration
-------------------------------------------------+-------------------------

Comment (by khag7):

 So we're juggling 3 values here:
 1. the initial php memory limit
 2. the raised memory limit (which might be higher than what's even
 physically possible)
 3. the ''actual'' available memory limit

 On one hand, it will be confusing to most users to show 3 values.
 On the other hand, information is beneficial. A "power user" might want to
 see all 3.

 I think showing `$ini_all['memory_limit']['global_value']` in site health
 is a good idea. Whether or not the initial and raised memory limits are
 also shown is probably not useful to the average user but maybe some
 people would like to see those as well. Who is the target audience for
 this?

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