New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Split code and save progress? OOM? #67

Closed

3 of 4 tasks

pionxzh opened this issue Dec 4, 2023 · 0 comments

Labels

enhancement performance

Owner

pionxzh commented Dec 4, 2023 •

edited

Loading

originally from #35

I have a 5Mb sized file that needs to be processed, I've tried running it directly in node and it takes up to 21G of memory space in some transform processing.

However, in some of the processing, it may fail, so maybe it would be possible to save the data that was processed successfully? And use it again next time?

This issue is used to track things we need to improve to prevent:

Lossing data when the unminified code is larger than 5MB (the size limit from LocalStorage)
OOM
Save the data more frequently to avoid the transformation failing half way and losing all the code we get

Consider storing data into IndexedDB #33
When the input is larger than a threshold, give user a warning that it might cause OOM
Performance improvement to reduce the memory usage and improve the speed.
Performance improvement and potential tools to adopt #35
Save the data more frequently

pionxzh added enhancement performance labels

pionxzh added a commit that referenced this issue


          feat(playground): add file size checker and warning

61c6ab7

#67

pionxzh added a commit that referenced this issue


          feat(cli): add file size checker and warning

f76be29

#67

pionxzh closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment