Are there any optimisations I can make when retrie...
# ask-metaflow
u
Are there any optimisations I can make when retrieving Run metadata using the api? I initialise the
Run
object then I want to access,
id
,
pathspec
and
data
. At the moment, each of these attributes can take ~2 seconds to respond. I want to check 1500 runs, so this will take a long time. Is there anything I can do?
1
v
that sounds abnormally slow. Typical time would be <100ms
is it that slow for all flows and runs or just for a particular one?
u
I have just dug a bit deeper and I think it is just an artefact of my location. I am in UK, server is in AUS. I think it is just round trip time. I just tried it on an ec2 instance in the same zone and it was as expected.
1
u
Thanks for responding
v
cool, that makes sense! 🌏