emscripten-core/emscripten

NODE_CODE_CACHING with dynamic libraries

Open

#12,752 opened on Nov 10, 2020

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C++ (3,519 forks)batch import
help wantedwontfix

Repository metrics

Stars
 (27,361 stars)
PR merge metrics
 (Avg merge 19d 10h) (147 merged PRs in 30d)

Description

Hi there,

Here is a feature request:

I am working on a NodeJS application, which starts up a relatively large Emscripten / WASM project, which uses several dynamically linked libraries (via the dynamicLibraries entry in the Module object). Currently, startup of the application takes several minutes. To speed things up, I imagine it would be very helpful to use NODE_CODE_CACHING=1. However, this only seems to work with the MAIN_MODULE (I get a *.cache.xxxxx file only for that type of module) and not with any SIDE_MODULE (there are no *.cache.xxxxx files).

Contributor guide

Research direction
Investigate how NODE CODE CACHING is implemented for MAIN MODULE in the Emscripten linker and compiler (emcc). Look for the cache generation logic and understand how it can be extended to SIDE MODULEs. Examine the existing `*.cache.xxxxx` file generation and identify the differences in the build process for MAIN MODULE vs SIDE MODULE.
Tech stack
cppwasmnodejs
Domain
toolingbuild systemperformance
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Node.jsEmscripten
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50