-
-
Notifications
You must be signed in to change notification settings - Fork 35.2k
28% binary size increase from v6.1.0 to v6.2.0 (with default configure options) #6860
Copy link
Copy link
Closed
Labels
buildIssues and PRs related to build files or the CI.Issues and PRs related to build files or the CI.i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.questionIssues that look for answers.Issues that look for answers.
Description
The node binary has increased in size quite noticeably from v6.1.0 to v6.2.0. Incremental size increases have been happening as more functionality's been added obviously, but this is quite a jump for a minor release.
$ docker run mhart/alpine-node:6.1.0 ls -l /usr/bin/node
-rwxr-xr-x 1 root root 22341392 May 6 16:31 /usr/bin/node
$ docker run mhart/alpine-node:6.2.0 ls -l /usr/bin/node
-rwxr-xr-x 1 root root 28704480 May 17 23:05 /usr/bin/node
(28.48% increase)
When compiled with --fully-static:
$ docker run mhart/alpine-node:base-6.1.0 ls -l /usr/bin/node
-rwxr-xr-x 1 root root 24726456 May 6 17:04 /usr/bin/node
$ docker run mhart/alpine-node:base-6.2.0 ls -l /usr/bin/node
-rwxr-xr-x 1 root root 30255656 May 17 23:27 /usr/bin/node
(22.36% increase)
Is this just something we have to live with, or has something gone awry here?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to build files or the CI.Issues and PRs related to build files or the CI.i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.questionIssues that look for answers.Issues that look for answers.