[Web][PROPOSAL]: implement ArtifactCache using OPFS #17510
Draft
+132
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
OPFS has better persistence, performance, and consistent support for large files across browsers.
Personally I would like to see this caching strategy for https://github.com/mlc-ai/web-llm.
This PR doesn't implement all required changes and hasn't been proved to work yet - I just created a PoC class implementing the
ArtifactCacheTemplate
.Potentially a problem with this approach would be that this cache uses OPFS on main thread with async APIs. A better solution could be to use Web Worker and sync file handlers - https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Origin_private_file_system#manipulating_the_opfs_from_a_web_worker. Both approaches could be valid for different use cases, so I propose creating 2 new caching strategies -
opfs
andopfs-worker
.I could finish the required work if we find it useful. Otherwise I would just move caching higher up in my stack and just do it for my specific use case.