I created a dashboard containing a filter that was linked to many other filters (about 7 others). The first time trying to click on the filter and revealing the dropdown values the dropdown hung and kept showing a spinning circle. It turns out that a query was executed on the backend to retrieve the dropdown list values and caused an extremely high CPU usage on my PostgresSQL db. Any clue why this hung, and what can be done to make sure this doesnt happen again? Since then I unlinked it to most of the the other filters and only linked it to 1, and I havent had issues. Does this have anything to do with the metabase scan tasks?
those filter values are gotten from the field_values table in the app db. So pretty sure the issue here is that your DB is underpowered or there's a massive amount of rows there