We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your peak memory usage when using WASM is your memory usage for the rest of time, see WebAssembly/design#1397
This means we need to load from IndexedDB in chunks, to reduce peak memory consumption.
The text was updated successfully, but these errors were encountered:
Not sure what exactly are the memory issues you face, but when working with large files in browser, Blob-s are very helpful.
To my experience, even when using dozen of GBs of data referenced via Blob, there are no memory peaks observed.
The downside of using Blobs are that:
I wonder if Blobs are suitable for your case.
Sorry, something went wrong.
Not sure what exactly are the memory issues you face, but when working with large files in browser, Blob-s are very helpful. To my experience, even when using dozen of GBs of data referenced via Blob, there are no memory peaks observed. The downside of using Blobs are that: access to the bytes is async the data are readonly, unless you decide to slice the source Blob to create another Blob object (which is a synchronous operation). I wonder if Blobs are suitable for your case.
I need to look into this! I'll take a look at Blobs thanks for the reminder.
No branches or pull requests
Your peak memory usage when using WASM is your memory usage for the rest of time, see WebAssembly/design#1397
This means we need to load from IndexedDB in chunks, to reduce peak memory consumption.
The text was updated successfully, but these errors were encountered: