[erlang-questions] code_change in the large

Mojito Sorbet <>
Mon Jun 20 00:21:12 CEST 2011


As I understand how code_change works, all processes using a module must
be suspended before the switch can happen, the code is purged and
reloaded, then they are all resumed.  The application upgrade support
takes care of the mechanics for this, but I wonder about the timing
implications when I have possibly tens of thousands of processes using
the same module.  Are there any numbers on this?





More information about the erlang-questions mailing list