diff options
| author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2023-11-04 00:10:42 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-03 23:10:42 +0000 |
| commit | f50377de7f087868dd481b4129694b85e3594ba6 (patch) | |
| tree | 27910f1b3ae6e65fdd51af952dfa7a702598e9a3 /bin | |
| parent | 8e96d3a051dc03864362ef2af523e86705444cae (diff) | |
| download | spack-f50377de7f087868dd481b4129694b85e3594ba6.tar.gz spack-f50377de7f087868dd481b4129694b85e3594ba6.tar.bz2 spack-f50377de7f087868dd481b4129694b85e3594ba6.tar.xz spack-f50377de7f087868dd481b4129694b85e3594ba6.zip | |
environment: solve one spec per child process (#40876)
Looking at the memory profiles of concurrent solves
for environment with unify:false, it seems memory
is only ramping up.
This exchange in the potassco mailing list:
https://sourceforge.net/p/potassco/mailman/potassco-users/thread/b55b5b8c2e8945409abb3fa3c935c27e%40lohn.at/#msg36517698
Seems to suggest that clingo doesn't release memory
until end of the application.
Since when unify:false we distribute work to processes,
here we give a maxtaskperchild=1, so we clean memory
after each solve.
Diffstat (limited to 'bin')
0 files changed, 0 insertions, 0 deletions