From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12426] NodeJS slow startup performance (~30s)
Date: Sun, 22 Dec 2019 18:02:03 +0000 [thread overview]
Message-ID: <bug-12426-163-jj4xzTuJgf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12426-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12426
--- Comment #6 from Eric Higgins <erichiggins@gmail.com> ---
All subsequent runs of nodejs are just as slow to start.
Storage is a class 10 microSD.
Actually, the prebuilt nodejs binaries are also dynamically linked. I found
this out the hard way because I was using uClibc-ng and the prebuilt expects
glibc.
(prebuilt)
# file /usr/local/lib/nodejs/node-v10.18.0-linux-armv6l/bin/node
/usr/local/lib/nodejs/node-v10.18.0-linux-armv6l/bin/node: ELF 32-bit LSB
executable, ARM, EABI5 version 1 (GNU/Linux), dynamically linked, interpreter
/lib/ld-linux-armhf.so.3, for GNU/Linux 3.16.42, with debug_info, not stripped
(compiled by buildroot)
# file /usr/bin/node
/usr/bin/node: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
dynamically linked, interpreter /lib/ld-uClibc.so.0, stripped
For what it's worth, the flags they use for armv6l are available here:
https://github.com/nodejs/unofficial-builds/tree/master/recipes/armv6l
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-12-22 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 14:52 [Buildroot] [Bug 12426] New: NodeJS slow startup performance (~30s) bugzilla at busybox.net
2019-12-20 14:57 ` [Buildroot] [Bug 12426] " 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 [this message]
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-jj4xzTuJgf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.