You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new IO code can at time utilize quite large amounts of memory. This is due to the fact that the process is so lightweight it never gets garbage collected. Thus, it is never seen that the binary() data it has is dead and be collected.
It can be verified by executing the following from a shell:
[garbage_collect(P) || P <- processes()].
This means we should probably build in some form of garbage collection into the system on a timer, so when a function has not been utilized for a short while, it will try to GC itself. Also, we should probably hack the fullsweep_after spawn_opt.
The text was updated successfully, but these errors were encountered:
The new IO code can at time utilize quite large amounts of memory. This is due to the fact that the process is so lightweight it never gets garbage collected. Thus, it is never seen that the binary() data it has is dead and be collected.
It can be verified by executing the following from a shell:
This means we should probably build in some form of garbage collection into the system on a timer, so when a function has not been utilized for a short while, it will try to GC itself. Also, we should probably hack the
fullsweep_after
spawn_opt.The text was updated successfully, but these errors were encountered: