Black Lives Matter. Please consider donating to Black Girls Code today.

Analyzing Memory Footprint of a Dash App

I noticed that the Memory Footprint is very high for a Dash app that I am currently developing (often 1-2 GB!).
The app uses a dcc.Dropdown component to run a simple SQL query and render some tables and charts.
Other dash apps that I’ve written are usually in the 100-300 MB range.
I’m having quite a bit of difficutly in tracking down and analyzing what exactly is resulting in such a high memory footprint (high enough that iOS Safari refuses to load the app).
Does anyone have any experience with Chrome’s Developer Tools and could advise on how to use it to see which react component might be contributing to this?

I’d like to know about this as well. I built a dashboard that works fine on Azure when it is first loaded, but over time, I see that RAM usage is constantly near 100% and performance is slow. Any sugestions?