| View previous topic :: View next topic |
| Author |
Message |
Princess Nell
l33t
Joined: 15 Apr 2005
Posts: 927
|
 Posted: Wed Dec 11, 2024 8:31 pm Post subject: nodejs compile time |
 |
|
Excerpt:
| Code: |
2017-05-05T21:37:48 >>> net-libs/nodejs-6.9.4: 8′43″
2018-04-15T19:19:29 >>> net-libs/nodejs-8.11.1: 17′30″
2019-11-23T23:42:46 >>> net-libs/nodejs-12.13.0: 10:02:58
2020-05-20T21:21:05 >>> net-libs/nodejs-14.2.0: 1:02:04
2022-05-21T19:52:36 >>> net-libs/nodejs-16.14.2: 59′15″
2022-06-18T21:22:48 >>> net-libs/nodejs-18.3.0: 1:13:32
2023-05-27T23:54:43 >>> net-libs/nodejs-20.2.0: 1:25:51
2024-07-13T21:33:24 >>> net-libs/nodejs-22.3.0: 2:50:16
2024-08-17T20:11:17 >>> net-libs/nodejs-22.4.1-r1: 3:19:54
2024-10-26T23:33:21 >>> net-libs/nodejs-22.4.1-r1: 2:45:26
|
To put this into context, the emerge history goes back at least one, if not two build machines, and each new box was faster than the previous. I'm willing to accept the 2nd last entry as an outlier, but do we have an explanation for the compile time for this ebuild? On my system, it is required by all things mozilla, direct and derived, so I can't avoid it.
| Code: |
Installed versions: 22.4.1-r1(0/22)^t(01:18:34 27/10/24)(icu npm snapshot ssl system-icu system-ssl -corepack -debug -doc -inspector -lto -pax-kernel -test CPU_FLAGS_X86="sse2")
|
I could probably disable npm, but not sure for how much gain. |
|
| Back to top |
|
 |
Banana
Moderator
Joined: 21 May 2004
Posts: 1792
Location: Germany
|
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20510
|
| Posted: Sat Dec 14, 2024 5:20 am Post subject: |
|
|
08:17:35 - 13 03:12:24
That was fun.
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
gorg86
Guru
Joined: 20 May 2011
Posts: 318
|
| Posted: Mon Dec 16, 2024 8:12 pm Post subject: |
|
|
| Post your emerge --info, those compile times are very long even for a potato PC. |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2027
|
| Posted: Mon Dec 16, 2024 8:45 pm Post subject: |
|
|
Someone reported this to me on IRC a few months ago and we did a little bit of digging. We found the substantial increase between iirc 20 and 22 started with an import of newer V8.
I filed a handful of GCC bugs (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116286, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116285) for some kind of slow compilations but they weren't smoking guns and I don't really feel like we got to the bottom of it. The difference for those 2 bugs I filed wasn't really ideal in terms of something we could easily reduce to make it more actionable, either. |
|
| Back to top |
|
|
bstaletic
Guru
Joined: 05 Apr 2014
Posts: 401
|
| Posted: Mon Dec 16, 2024 8:48 pm Post subject: |
|
|
Those times match mine:
| qlop -vtm nodejs: | 2023-05-01T01:35:20 >>> net-libs/nodejs-20.0.0: 1:32:03
2023-05-09T20:13:52 >>> net-libs/nodejs-20.1.0: 1:33:35
2023-05-18T21:38:58 >>> net-libs/nodejs-20.2.0: 1:26:32
2023-07-01T06:27:01 >>> net-libs/nodejs-20.3.1: 1:29:50
2023-08-13T12:01:04 >>> net-libs/nodejs-20.5.1: 1:31:38
2023-09-10T09:07:16 >>> net-libs/nodejs-20.6.0: 1:47:03
2023-09-13T17:40:33 >>> net-libs/nodejs-20.6.1: 1:35:12
2023-09-30T12:46:06 >>> net-libs/nodejs-20.7.0: 1:28:57
2023-10-23T08:42:28 >>> net-libs/nodejs-20.8.1: 1:27:23
2023-12-14T07:43:39 >>> net-libs/nodejs-20.9.0: 1:22:38
2024-01-29T02:05:34 >>> net-libs/nodejs-20.11.0: 1:26:11
2024-03-05T00:02:17 >>> net-libs/nodejs-20.11.1: 1:20:58
2024-08-05T16:15:26 >>> net-libs/nodejs-22.5.1: 3:14:25
2024-08-21T08:51:24 >>> net-libs/nodejs-22.6.0: 2:53:33
2024-08-31T23:00:21 >>> net-libs/nodejs-22.7.0: 3:12:56
2024-09-17T09:37:26 >>> net-libs/nodejs-22.8.0: 2:52:32
2024-11-11T20:38:17 >>> net-libs/nodejs-22.10.0: 3:17:04 |
nodejs is a massive pain in the ass to compile. I did at some point turn on LTO globally. |
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20510
|
| Posted: Wed Dec 18, 2024 4:46 am Post subject: |
|
|
| gorg86 wrote: | | Post your emerge --info, those compile times are very long even for a potato PC. |
If that's regarding mine, the results are a bit misleading. I had forgotten that I changed from -j3 to -j1 to prevent intermittent failures. It has been building with -j1 for some time... I'll try -j2 to see it works.
It seems likely that I switched from -j3 to -j1 with nodejs-20.5.1: | Code: | net-libs/nodejs-20.2.0: 1:29:57
net-libs/nodejs-20.2.0: 1:35:28
net-libs/nodejs-20.2.0: 1:33:24
net-libs/nodejs-20.5.1: 4:10:36
net-libs/nodejs-20.6.1: 4:18:17
net-libs/nodejs-20.11.0: 4:12:00
net-libs/nodejs-20.11.0: 4:28:08
net-libs/nodejs-20.12.1: 4:02:24
net-libs/nodejs-22.3.0: 6:53:02
net-libs/nodejs-22.4.1-r1: 6:56:54
net-libs/nodejs-22.4.1-r1: 6:55:44
net-libs/nodejs-22.4.1-r1: 6:54:49 |
I've been delaying an icu induced rebuild of nodejs / firefox, so I'll see what happens later this week.
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2511
|
| Posted: Wed Dec 18, 2024 6:19 am Post subject: |
|
|
With the consideration I'm assuming most of the commenters here do not seem to need nodejs for something other than a build time dependency, I would urge moving to binary packages for the ones that require nodejs as a build dependency. Nodejs is too big of a crap to waste any amount of time on it.
p.s. I hate that piece of .... for it made so much more .... possible. If it wasn't for firefox and calibre, it wouldn't exist on my computer.
Best Regards,
Georgi |
|
| Back to top |
|
|
|
Portage & Programming
