This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Freeze initialized runtime state for use in subsequent executions. #78
Labels
You can continue the conversation there. Go to discussion →
This is based on a discusssion @markshannon and I had the other day, but it also relates to discussions I've had with other core devs periodically for several years.
The idea is to start up the runtime, finish initialization, and then take a snapshot of the process memory (or a subset). That snapshot is then rendered as a header file (a la frozen modules) which the runtime can use on subsequent executions to get to that initialized state instead of executing all the usual runtime code. (This is reminiscent of a technique xemacs uses.)
Benefits
Caveats and Challenges
Open Questions
The text was updated successfully, but these errors were encountered: