From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12426] New: NodeJS slow startup performance (~30s)
Date: Fri, 20 Dec 2019 14:52:14 +0000 [thread overview]
Message-ID: <bug-12426-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12426
Bug ID: 12426
Summary: NodeJS slow startup performance (~30s)
Product: buildroot
Version: 2019.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: erichiggins at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The performance of the NodeJS executable, as compiled by Buildroot, has
exceptionally poor startup performance, taking around 30s to run.
The prebuilt binaries from NodeJS running on the same system take less than 2s
to run.
I created a Gist with a comparison using the time command:
https://gist.github.com/erichiggins/ac139ebe34b8d3c6dbb68f3b09ca9008
In both cases, the runtime performance is about equal.
The prebuilt binaries require the buildroot system to use glibc and will not
run if a more space-efficient alternative (uClibc-ng) is selected.
Further, NodeJS v12.x (now the major version used by Buildroot) does not
officially support ARM v6l and is considered experimental.
https://github.com/nodejs/build/issues/1677#issuecomment-486204349
Current workaround is to use glibc and overwrite the NodeJS executables with
the unofficial prebuilts via rootfs overlay.
https://github.com/nodejs/unofficial-builds/
It would be quite helpful to build a performant NodeJS executable without
requiring these workarounds.
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-12-20 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 14:52 bugzilla at busybox.net [this message]
2019-12-20 14:57 ` [Buildroot] [Bug 12426] NodeJS slow startup performance (~30s) bugzilla at busybox.net
2019-12-20 15:14 ` bugzilla at busybox.net
2019-12-20 18:52 ` bugzilla at busybox.net
2019-12-22 15:49 ` bugzilla at busybox.net
2019-12-22 16:50 ` bugzilla at busybox.net
2019-12-22 18:02 ` bugzilla at busybox.net
2019-12-22 18:28 ` bugzilla at busybox.net
2019-12-22 19:53 ` bugzilla at busybox.net
2019-12-24 21:32 ` bugzilla at busybox.net
2024-06-15 14:52 ` bugzilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12426-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox