Please bring back the min + max memory values in the Performance Profiler

43 views
Skip to first unread message

Leon Sorokin

unread,
Jun 24, 2025, 2:08:04 AMJun 24
to devtools-dev
Hello!

As someone who spends a lot of my 9-5 in the Performance tab, I'm finding some recent removals of various summary stats to be a significant UX regression. There are two changes in particular that I find most frustrating.

1. For a selected time range, the min + max heap, nodes, listeners

Since the memory graph has no y axes, it's impossible to compare two similar sawtooth patterns. I'm frequently interested in the delta of the allocations before and after an optimization, but without any kind of numeric values [and without meticulous mouse hover interaction] a sawtooth delta of 10mb looks the same as 1mb delta.

2. Idle time that used to exist in the pie chart view.

Often, I try to optimize for increasing idle time for the same task. This sometimes means trading scripting costs for more favorable rendering costs, or moving some work into the "system" category. It is important to have a sum somewhere that shows total cpu time (or idle time) needed to perform the same task, e.g. scrolling a virtualized table for 10s. TBH, the pie chart was a much better breakdown visualization that what replaced it; FWIW, I say this as a principal DataViz engineer at Grafana.

The removal of these two items makes it very difficult to see, compare, and impossible to share screenshots of before/after that shows how performance has improved or degraded overall. I'd really appreciate if these metrics were restored in the UI.

thanks,
Leon
Screenshot_20250622_165317.png
Screenshot_20250623_104339.png
Screenshot_20250623_104236.png

Jack Franklin

unread,
Jun 24, 2025, 2:23:04 AMJun 24
to Leon Sorokin, devtools-dev
Hey Leon,

Thanks for reaching out to the mailing list. This is really helpful feedback so thank you for taking the time to send it.

Firstly, the missing numbers on the memory graph is a bug, and not a deliberate change. I have logged crbug.com/427329460 to track and fix that work.

RE the removal of Idle time, thanks for the feedback. We made the change at the time because we felt it was unnecessary to explicitly list idle time, but I can see via your use case that it's worth reconsidering. I'll send your feedback to a couple of folks on the team to get their opinions and come back to you.

Thanks,

Jack.



--
You received this message because you are subscribed to the Google Groups "devtools-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to devtools-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/devtools-dev/0f4a4a8e-06dd-4bcf-b972-bce03ef1f74dn%40chromium.org.

Leon Sorokin

unread,
Jun 24, 2025, 11:58:21 AMJun 24
to devtools-dev, jacktf...@chromium.org, devtools-dev, Leon Sorokin
Thanks Jack, that's great to hear, and thanks for the super fast fix!

Glad I found the right forum for nerd-sniping feeback :P
Reply all
Reply to author
Forward
0 new messages