> Doing an open requires all things to be in-memory.
It only requires that the zip file be accessible, either in-memory or on-disk.
Your introduction says that you originally had the zip file *and* the decompressed files in memory, ZipFile.open avoids the latter. Furthermore the small bit of code you post in the conclusion seems to hint that you still have the zip file in memory when you do the extraction.
And again, you can use ZipFile.open just fine if you have the zip file on-disk, it's still lazy.
Doing an open requires all things to be in-memory. It's a bit faster but would require me to have a much beefier server, which might be the best course of action actually.
Comment
> Doing an open requires all things to be in-memory.
It only requires that the zip file be accessible, either in-memory or on-disk.
Your introduction says that you originally had the zip file *and* the decompressed files in memory, ZipFile.open avoids the latter. Furthermore the small bit of code you post in the conclusion seems to hint that you still have the zip file in memory when you do the extraction.
And again, you can use ZipFile.open just fine if you have the zip file on-disk, it's still lazy.
Parent comment
Doing an open requires all things to be in-memory. It's a bit faster but would require me to have a much beefier server, which might be the best course of action actually.