Editing
Erlang Hot Code Reloading
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== How Hot Code Reloading Works === Hot code reloading in Elixir is made possible by the way the Erlang virtual machine (BEAM) handles running processes and code changes. When a process is started, it runs within its own isolated execution environment called a [[Process (computing)|process]]. Each process has its own memory space and executes code independently, allowing for individual updates of code without affecting other parts of the system. To perform hot code reloading, developers typically follow these steps: 1. Modify the code: Make the necessary changes to the source code. 2. Recompile: Compile the updated code into BEAM bytecode. 3. Load the updated code: Load the new code into the running system. 4. Apply changes: Trigger the hot code reloading process to apply the changes to the appropriate processes. 5. Verify the changes: Test and verify that the changes have taken effect as expected.
Summary:
Please note that all contributions to Elixir Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Elixir Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information