Beast Modes Affecting Card Performance

Hello,

I'm curious if anyone else has noticed degraded performance making and editing cards due to the amount of beast modes on the dataset/card?

We are trying to isolate this issue with some of our datasets, and try moving calculated field logic down to the ETL to come through as a column.

Has anyone else experienced or tried this?

Thanks,

Cole