-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
memory consumption unpredictible #114037
Comments
The title says memory consumption is unpredictable, but the issue says memory consumption is quite predictable. Which is it? I adjusted the labels anticipating the answer is something like "Build parallelism produces shocking increase in memory usage" which is a statement I would certainly agree with. I'd like to reproduce the memory usage in question. How would I do that? I tried to run
|
@saethlin, with unpredictable i ment: cannot say in advance that it uses so much memory, and does not restrict itself to the memory in the system. but you are absolutely right, running it a second time uses again more than 8GB. would what is mentioned in the readme work for you?
on arch linux the following works for me, sometimes:
the PKGBUILD file specifies how this is run, https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=cosmic-epoch-git. when using 4 build jobs as the processor would allow by default, linking uses all the time more than 8gb. |
Hm, I can't reproduce 8 GB peak memory usage, I consistently only see 2.8 GB. I'm on Arch, running |
at some point it arrives at building 3 binaries at once:
and - very cool - it now does not run out of memory any more. |
@saethlin cosmic desktop now got split up into single components, entry point is: for me it fell over with out of memory when building the dependent cosmic-applets, on 2024.07.21. am leaving the ticket closed, as it was one time. |
when compiling software like cosmic-epoch:
https://github.com/pop-os/cosmic-epoch
on a laptop with 8GB and default settings, rust toolchain fails when linking the binaries, as no memory is left. there is an option to only use 1 of the 4 cores, but this is a setting for both, compiling and linking.
would be cool if by default, the rust toolchain would be aware how much memory there is and use all the threads for compile, but restrict itself to a max memory for linking.
The text was updated successfully, but these errors were encountered: