I'm not sure how much of an antipattern this is, b...
# flyte-support
f
I'm not sure how much of an antipattern this is, but I've been thinking about creating an EFS based PVC for each flyte namespace and using it to pass large objects rather than having to do a S3 upload/download between tasks. It breaks the idea of tasks being fully independent outside of the DAG connection, but I'm building a LMDB for ML inference in one task and then passing it to a GPU task for inference and IO on 500G files can be quite slow
f
This is fine
We did this for some cars where raw output prefix is set to local path
But this will be slow too
I don’t think Efs is way faster than s3
f
It would be faster if only because it's write->read rather than write->upload->download->read
f
ohh you dont have to upload /download thing. you can simply stream right?
and in the next release working on getting the rust storage layer - that will make it even faster
f
Between tasks? Isn't it a forced S3 IO step?
ohh ya not between tasks
i see you will run both tasks too