On 8/26/2018 6:43 PM, Jonathan Simpson wrote:
The fact that Racket isn't releasing the memory back to the OS appears to be causing the system to eventually run out of physical pages.
Is this a cloud server? Is the problem that the "out-of-memory" (OOM) handler is killing processes? That won't happen if you provide a swap space to cover over-commit spikes (or prevent them a priori with ulimit). In any event you probably should disable the OOM killer and adjust the kernel's over-commit behavior to something reasonable.
see: https://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html http://engineering.pivotal.io/post/virtual_memory_settings_in_linux_-_the_problem_with_overcommit/ https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/s-memory-captun George -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
