Amanda Wee
12/16/2020, 3:13 AMChris White
flow.run
, but honestly we don’t generally recommend using that for long-running or production flows - note that if you use any task caching then the cache is held in-memory with flow.run
, so that could explain it; when you switch to orchestrating / scheduling with a Prefect backend, then each individual run of the flow will be submitted to its own subprocess (when using the local agent), in which case your run’s memory will get cleaned up naturally when complete, so I think you should be good to go once you migrate to the new pattern!Amanda Wee
12/16/2020, 6:10 AMChris White