Hi all, we’re using the metaflow ui to inspect our flows and have noticed a big slow down in loading results. We’re getting a lot of 504s, despite loading fairly small cards/outputs. I have a feeling the backend has too much data in it, but wanted to check here first. do you recommend caching the metadata of older runs periodically, or something else?

Last week a related question got asked

I think Metaflow recently released some new version of the metadata service. I believe (not 100% on it) this included some performance improvements. Perhaps it is worth updating?

@mammoth-rainbow-82717 is right. There was a new version of metaflow-ui that was released last week that makes fewer requests to the backend and should ease some pressure. @astonishing-jewelry-18059 what version are you currently running? (Click on quick links to see)

we are using

Application version: v1.1.2

. Will look into updating the metaflow-ui, thanks! What is odd is that we have two environments deployed (both with the same version). One can load the requests just fine, the other is the one that is 504ing. The latter is the one with a lot more data, so that’s why i was wondering if we need to be caching (similar to @orange-secretary-61629’s question)

@astonishing-jewelry-18059 - we shipped a few updates to the database schema that would require you to do perform a migration. That should help with speeding up many views.