-
Notifications
You must be signed in to change notification settings - Fork 83
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Raise minimum required resources (RAM) per CPU core #1191
Comments
tdruez
added a commit
that referenced
this issue
Apr 30, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
Apr 30, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
Apr 30, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 2, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 6, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 6, 2024
Signed-off-by: tdruez <tdruez@nexb.com>
tdruez
added a commit
that referenced
this issue
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After some investigation on the "A process in the process pool was terminated abruptly while the future was running or pending." type of error while running the
scan_codebase
pipeline, I've noticed that each process needs around 2GB of RAM at the moment instead of the 1GB recommended in the docs.This is mainly caused by the
licensedcode.cache.get_cache
call that loads an index in the memory of each process. Ideally, this index should be shared. See aboutcode-org/scancode-toolkit#3755The text was updated successfully, but these errors were encountered: