-
Notifications
You must be signed in to change notification settings - Fork 562
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.
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
When the compiler get's killed by OOM/SIGTERM the cache-db.json file is not updated #3995
Comments
gorbak25
changed the title
When the compiler get's killed by OOM the cache-db.json file is not updated
When the compiler get's killed by OOM/SIGTERM the cache-db.json file is not updated
Jan 21, 2021
This sounds sensible to me, but we'll have to be really careful to avoid race conditions if we implement this, since modules are compiled in parallel. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When building large purescript codebases such as https://github.com/erlscripten/erlps-stdlib it's very easy to get killed by OOM - The modules are compiled in parallel usually exceeding the amount of RAM available on the system(I will open separate issues with the results of my investigation/profiling data - for instance the lexer right now uses up a lot of memory on large files). What is really troublesome is that if the compilation gets killed by OOM after compiling a lot of heavy modules then on the next run they will get recompiled although they compiled successfully. After investivating the purescript codebase the cache-db.json file is only updated after all of the compiler tasks either succeed or failed - this is not a problem for small projects but when the compilation times become significant(https://github.com/erlscripten/erlps-stdlib) it's really troublesome :(
To Reproduce
Expected behavior
PureScript version
Tried both on 0.13.8 and on the current master branch :(
The text was updated successfully, but these errors were encountered: