You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
The "IPLD Data Importers" endeavor is the effort to create IPLD (or even unixfs) data structures out of various kinds of data.
Motivation:
The idea is that chunking POSIX files based on things like Rabin Fingerprinting is good but not great, and that many times we can be much smarter about the files, chunking them by taking into account the file's internal structure. Doing this for a few of the most important file formats may see huge dedup winnings (tar archives, VM images, containers, ...).
Examples:
If importing a .tar archive into ipfs, import it s.t. (a) each tar header is an object, and (b) each file is fed back into the importer(s).
If importing a video, maybe we can chunk intelligently around (a) container formats, (b) key frames, etc.
If importing a VM image, maybe we can chunk s.t. we import the filesystem itself correctly.
The "IPLD Data Importers" endeavor is the effort to create IPLD (or even unixfs) data structures out of various kinds of data.
Motivation:
The idea is that chunking POSIX files based on things like Rabin Fingerprinting is good but not great, and that many times we can be much smarter about the files, chunking them by taking into account the file's internal structure. Doing this for a few of the most important file formats may see huge dedup winnings (tar archives, VM images, containers, ...).
Examples:
.tar
archive into ipfs, import it s.t. (a) each tar header is an object, and (b) each file is fed back into the importer(s).Notes:
Diagram:
The text was updated successfully, but these errors were encountered: