You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the new "Memory Allocator" page we have the column Max carrier size. We use the max value returned by the BEAM.
However, the :observer.start() set the max value since the page is shown (or since the observer started), not from the start of the BEAM. I think we can reproduce the same behaviour by keeping a list of the max value per row, in a similar way we do to calculate the reductions:
In the new "Memory Allocator" page we have the column Max carrier size. We use the max value returned by the BEAM.
However, the
:observer.start()
set the max value since the page is shown (or since the observer started), not from the start of the BEAM. I think we can reproduce the same behaviour by keeping a list of the max value per row, in a similar way we do to calculate the reductions:phoenix_live_dashboard/lib/phoenix/live_dashboard/system_info.ex
Lines 47 to 57 in da3272d
The question is, do we want that behavior? Or do we want an extra column?
The text was updated successfully, but these errors were encountered: