Hello, With the help from the threads here, especi...
# ask-metaflow
g
Hello, With the help from the threads here, especially the one from @fresh-laptop-72652 (Thanks a lot 🙏), I was able to mount larger volumes to root 🙂 Right after I noticed tmpfs support was added for batch. Is this the recommended way instead of launch templates if all a user care about is storage? As one would still want to use launch templates to modify ECS clean up tasks etc. Any thoughts here. Thanks!
1
v
good to hear that you got it working! 🤗
tmpfs
is a convenient (and fast) option when you don’t need large amounts of disk space but just some fast scratch space
metaflow.S3
will use it automatically for its temp space, if you enable it
we’ll add proper docs for it soon - the feature is fully supported and available in the latest version
❤️ 1
g
For our usecase, we run an sdk that expects videos in a certain format - on disk, and the videos and artifacts could sum upto 20 GB. So unfortunately I am unable to use the full merits of metaflow.s3 saving data to page cache (I have to move them to specific location with specific name). I shall try to use tmpfs without launch template hope it goes smooth 🙂
v
it should be very easy: just do
@batch(use_tmpfs=True)
by default it allocates 50% of
@resources(memory=)
to tmpfs but the memory is only used when you store something to the volume
if you use
metaflow.S3
it uses it automatically. If you want to use tmpfs for your own purposes, you can find the mountpoint at
current.tempdir
❤️ 1
thankyou 1
g
Didn't know about current.tempdir, thank you!
v
it’s all new so practically no one knows about it 😅 docs coming soon
❤️ 1
among us party 1