View previous topic :: View next topic |
Author |
Message |
logrusx Advocate
![Advocate Advocate](/images/ranks/rank-G-1-advocate.gif)
![](images/avatars/176594205966916859b5145.jpg)
Joined: 22 Feb 2018 Posts: 2703
|
Posted: Thu Feb 06, 2025 7:28 pm Post subject: |
|
|
Code: | MiB Mem : 27908.0 total, 238.2 free, 27721.8 used, 381.7 buff/cache
MiB Swap: 65536.0 total, 32308.3 free, 33227.7 used. 186.2 avail Mem
|
Code: | PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2254082 portage 20 0 38.3g 19.1g 1108 S 31.2 70.1 12:12.51 TensileCreateLi |
Is there any reason you would want to build this monster? Can't you find a binary version from somewhere? What do you need it for? If it's absolutely necessary go buy a 128GB kit and hope for the best.
p.s. had I noticed how much memory it was taking I would have terminated it earlier, but now I'm willing to let it go and give you the binary. Hopefully my 5800H has the same flags as your 5600, because I have -march=native in make.conf.
Best Regards,
Georgi |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
logrusx Advocate
![Advocate Advocate](/images/ranks/rank-G-1-advocate.gif)
![](images/avatars/176594205966916859b5145.jpg)
Joined: 22 Feb 2018 Posts: 2703
|
Posted: Thu Feb 06, 2025 8:18 pm Post subject: |
|
|
I'm sorry but that's going for far too long and I have no way of knowing how much longer so I have to terminate it. Maybe try to disable gfx942 and if that doesn't work, then gfx941, gfx940 AMDGPU_TARGETS.
I see this ebuild is marked N and you're running a world update, are you sure you really need it?
EDIT: just as I wrote that, before terminating it, fans sped up through the roof and I was curious if it'll finish soon.
Here's what I saw:
Code: | PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2291592 portage 20 0 166900 143216 4012 R 86.8 0.5 3:53.40 python3.12
2291613 portage 20 0 175556 150832 4216 R 86.4 0.5 3:54.25 python3.12
2291615 portage 20 0 171904 148044 3992 R 86.4 0.5 3:54.58 python3.12
2291589 portage 20 0 166684 143228 3544 S 86.1 0.5 3:54.14 python3.12
2291595 portage 20 0 168292 145124 3888 S 84.4 0.5 3:54.09 python3.12
2291611 portage 20 0 168248 143708 4132 R 84.4 0.5 3:55.68 python3.12
2291617 portage 20 0 166968 143552 4372 R 84.4 0.5 3:53.53 python3.12
2291600 portage 20 0 178168 155252 3820 R 84.1 0.5 3:52.95 python3.12
2291608 portage 20 0 173864 150240 3780 R 84.1 0.5 3:55.11 python3.12
2291606 portage 20 0 172232 148204 3664 R 82.8 0.5 3:55.49 python3.12
2291602 portage 20 0 166388 143204 3820 R 82.1 0.5 3:54.63 python3.12
2291604 portage 20 0 167864 143696 3876 S 81.8 0.5 3:53.62 python3.12
2291612 portage 20 0 167284 143088 3608 R 81.1 0.5 3:55.84 python3.12
2291616 portage 20 0 167896 144428 3732 R 80.5 0.5 3:53.97 python3.12
2291598 portage 20 0 171476 148368 3592 R 79.8 0.5 3:53.89 python3.12
2291614 portage 20 0 174220 151148 3712 S 78.8 0.5 3:55.08 python3.12
2215213 joro 20 0 3268360 105648 24108 S 4.3 0.4 15:22.19 Hyprland
2254082 portage 20 0 45.2g 16.9g 3200 S 3.6 62.0 35:30.34 TensileCreateLi
2359157 portage 20 0 232344 58956 50764 R 3.3 0.2 0:00.10 clang++
2359159 portage 20 0 231396 57988 50308 R 2.3 0.2 0:00.07 clang++
2359160 portage 20 0 231976 57940 50260 R 2.0 0.2 0:00.06 clang++
121 root 20 0 0 0 0 S 1.7 0.0 24:16.06 kswapd0
|
In reality it runs more threads than make is instructed. Maybe make jobs are only 16 but some of them invoke other jobs too, so this package's build system doesn't seem to respect those. And it's likely not easy to make it do so. I'll wait just a little bit more as I hope this is the final stage of the compilation of the final target - gfx942.
EDIT2: I'm sorry, I gave it more than 40 minutes to finish, it didn't. After more than 2 hours compile time total and hundreds of gigabytes, if not terabytes wasted write cycles for this package only, I'm terminating it.
If you want to compile it badly, setup 64 GB swap and let it do its job. Have that in mind too:
Code: | du -sh /var/tmp/portage/sci-libs/hipBLASLt-6.1.1-r1
33G /var/tmp/portage/sci-libs/hipBLASLt-6.1.1-r1
|
Best Regards,
Georgi |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
Zucca Moderator
![Moderator Moderator](/images/ranks/rank-mod.gif)
![](images/avatars/8484577066727ff6a19116.gif)
Joined: 14 Jun 2007 Posts: 3939 Location: Rasi, Finland
|
Posted: Thu Feb 06, 2025 9:17 pm Post subject: |
|
|
logrusx wrote: | If it's absolutely necessary go buy a 128GB kit and hope for the best. | As it happens I just bought a workstation and stuffed it with 256GB of RAM. Although I don't have a working Gentoo install on it just yet.
But... I just cannot believe the memory requirements. Some build processes requiring 16GB seem realistic with big projects, and maybe 32GB. Something requiring something between 64GB or even 128GB is just not real.
I'd say with quite high confidence that the build system is broken... or the ebuild has some nasty bug.
I could be wrong. I haven't looked too deep into this. _________________ ..: Zucca :..
My gentoo installs: | init=/sbin/openrc-init
-systemd -logind -elogind seatd |
Quote: | I am NaN! I am a man! |
|
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
logrusx Advocate
![Advocate Advocate](/images/ranks/rank-G-1-advocate.gif)
![](images/avatars/176594205966916859b5145.jpg)
Joined: 22 Feb 2018 Posts: 2703
|
Posted: Fri Feb 07, 2025 8:12 am Post subject: |
|
|
Zucca wrote: | logrusx wrote: | If it's absolutely necessary go buy a 128GB kit and hope for the best. | As it happens I just bought a workstation and stuffed it with 256GB of RAM. |
From what I saw last night, 64GB might suffice even without swap, but swap better be there to prevent OOMs that might arise for a few hundred megabytes shortage.
Zucca wrote: | But... I just cannot believe the memory requirements. Some build processes requiring 16GB seem realistic with big projects, and maybe 32GB. Something requiring something between 64GB or even 128GB is just not real.
I'd say with quite high confidence that the build system is broken... or the ebuild has some nasty bug.
I could be wrong. I haven't looked too deep into this. |
This is not a normal build process. This is not a compiler. This is more like building a model, so the perspective you're looking from is not the right one. Just like when I tried to run Llama. When it didn't fit the GPU memory it simply run on the CPU. This is not a bug but a different type of software wrt it doesn't build executables but a model and it doesn't compile source but generates that model. And it doesn't use a compiler.
Best Regards,
Georgi |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|