Choosing Nim's Memory Management: Boehm GC, ARC, or Manual Mode
Learn how to pick Nim's garbage‑collection model—Boehm GC, ARC, or manual—based on latency, determinism, and C interop, with a concrete ARC file‑closure example.
Loading…
ReadMeFeed / Community knowledge
#gc
Real questions. Useful conversations. Find the people who know your stack.
Choosing Nim's Memory Management Model for Performance‑Sensitive Applications
A decision guide that compares Nim's GC, ARC, ORC, and manual memory modes, shows trade‑offs, and gives a concrete compile‑and‑measure workflow.
Limits: Space_Overhead Tuning for Low‑Traffic OCaml 5 Services
The goal is to lower the cloud bill for a native‑compiled OCaml service that receives only a handful of requests per hour. The primary knob is Gc.set ’s space_overhead parameter, which controls how aggressively the major GC runs: a higher value means fewer collections but a larger heap, while a lower value forces more frequent collections and a smaller heap.
ocamlGleam ↔ Erlang BEAM GC: Memory Leak Fix and Unresolved Struct Serialization Decision
Gleam compiles to Erlang bytecode, so its long‑running processes are subject to BEAM’s garbage collector. A community‑reported leak in the standard library’s map implementation can cause heap size to grow steadily, even though the code itself never retains explicit references. The proposed fix replaces mutable maps with copy‑on‑write semantics, which has sho
erlang
gleamWhich Python memory‑leak patterns persist in CPython 3.12?
Goal: Identify the exact memory‑leak scenarios that remain in CPython 3.12 when reference cycles involve objects that define a __del__ method. Constraints: CPython’s garbage collector does not automatically break cycles that contain __del__ methods, potentially leaving objects alive until the interpreter exits. This behavior is documented but not universally
python