Does someone else have the problem that loading asset status (of partitioned assets) is really slow in dagit? If I try to view backfills or assets with partitions I am only looking at spinners.

Hi there! There could be a handful of reasons for this depending on how you deploy Dagster. To help you deduce why, mind answering a couple questions? Are you self-hosting Dagster or using Dagster Cloud? If you're self-hosting, how so and what resources are using to deploy it?

Curious how large your asset graph is as well? And how many partitions each asset has/which partition defs are being used? We did add an optional migration in

1.1.4

that basically caches your partition statuses and enables loading the asset graph more quickly. I'd recommend running this migration via

dagster instance migrate

if you haven't already.

Hey, thanks for the answers. It's local, until now I just started everything with

dagster dev

but I'll move it to some proper deployment soonish. I think there was a problem with the process, after restarting everything works better now. I have only 7 assets with 4k partitions max. (all dynamic). Had the problems on a 64 core machine.

Ok! glad it works better now