Open
Conversation
Member
|
There's also the new WasmFS system we are building that should be able to handle larger files via its JS backend. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello,
From wasm currently there is no easy way to generate large output files. MEMFS based approaches are all limited to the size of available memory.
This small patch adds a postMessage to WORKERFS' stream_ops.write callback, on predefined entries passed in at mount time, called "writables", alongside the existing "files" and "blobs" arguments, which semantically are writeonly files that can be persisted or streamed in browswer context in the onmessage handler.
While the patch is apparently not intended for merging, I'm looking for feedback on how this can be taken forward.
I've looked at @connorjclark 's fsfs PR and that is also depending on MEMFS so it cannot solve the problem.
This patch is verified to work as intended in handling large output files in my ffmpeg wasm app.
Thanks,