ReadMeFeed / Community knowledge

#garbage-collection

Real questions. Useful conversations. Find the people who know your stack.

Editorial question143.6K views1,947 votes1 answer2,871 following

AI-generated

Lua garbage collection vs. manual object pooling for low-traffic workloads

In LÖ2D, maintaining a consistent frame rate on resource-constrained hardware requires managing how the underlying Lua garbage collector (GC) handles memory. While the framework is inherently lightweight, the non-deterministic nature of the GC can cause unpredictable micro-stutters if collection cycles trigger during intensive frames. To mitigate this, devel

garbage-collection

lua performanceTasadduq Burneyowner28K rep · 12 Jul 2026, 23:25 UTC

Editorial question33.1K views2,446 votes0 answers3,932 following

AI-generated

Incremental marking vs parallel scavenger: trade‑off for pause‑time variability in latency‑sensitive Node.js

The goal is to minimize GC‑induced pause‑time variability for latency‑sensitive Node.js workloads that allocate many short‑lived objects (e.g., Buffers in a tight loop). The constraint is choosing between V8’s incremental (Orinoco) marker, which spreads marking work to lower worst‑case pauses but adds write‑barrier overhead, and the parallel young‑generation

parallel-scavenger garbage-collection

v8Tasadduq Burneyowner28K rep · 28 May 2026, 17:41 UTC

Editorial question53K views2,387 votes1 answer2,421 following

AI-generated

Can manual gc.collect() calls reduce RSS growth in low-traffic workloads?

In low-traffic Python applications, minimizing resource overhead is critical for cost reduction. While CPython primarily relies on reference counting for immediate object reclamation, the cyclic garbage collector (gc module) is required to resolve reference cycles that would otherwise lead to memory leaks. There is a trade-off between the CPU overhead of aut

garbage-collection

python cpythonTasadduq Burneyowner28K rep · 07 Mar 2025, 03:09 UTC

Editorial question36.2K views3,813 votes1 answer3,928 following

AI-generated

Memory leak symptoms in Boehm GC conservative scanning

Conservative Garbage Collection in Crystal Crystal relies on the Boehm-Demers-Weiser conservative garbage collector to manage heap memory. Because this GC is non-generational and non-compacting, it identifies reachable objects by scanning the stack and registers for any word that resembles a valid heap address. Heap Retention Uncertainty In applications util

garbage-collection boehm-gc

crystalTasadduq Burneyowner28K rep · 12 Dec 2024, 08:40 UTC

Editorial question39K views2,320 votes1 answer2,615 following

AI-generated

cannot allocate vector of size: Memory exhaustion during data.frame modification

Memory Allocation in R Data Frames R employs a copy-on-modify semantic for data.frame objects. When a column is added or a subset of rows is modified, the environment may trigger a full duplication of the object in memory to maintain data integrity. In scenarios involving large datasets that approach the limits of available system RAM, this behavior can lead

data-frame garbage-collection

rTasadduq Burneyowner28K rep · 01 Aug 2024, 18:47 UTC

Editorial question97.9K views2,080 votes1 answer1 comment3,769 following

AI-generated

Persistence of stateful data during NixOS garbage collection

NixOS maintains system immutability by storing configurations in the /nix/store . While system generations are atomic and easily reversible, stateful data—such as database directories, log files, or persistent user configurations—typically reside outside the immutable store to survive transitions. A challenge arises when using nix-collect-garbage to prune ol

garbage-collection declarative-config

nixosAri Finch0 rep · 06 Jul 2024, 06:00 UTC

Editorial question38.9K views4,512 votes1 answer3,317 following

AI-generated

NixOS Automatic GC and Generation Retention: Bootloader Limit Behavior Needs Diagnosis

Retention Boundaries Between Boot Menu Limits and Store Deletion NixOS derives system state from a declarative configuration and keeps prior generations in the Nix store so rollbacks remain possible. Garbage collection is not automatic unless a systemd timer or manual invocation triggers it, while the bootloader's configurationLimit controls how many generat

garbage-collection nix-store

nixosTasadduq Burneyowner28K rep · 20 Nov 2023, 12:51 UTC

Editorial question117.6K views1,823 votes1 answer4,569 following

AI-generated

Container image garbage collection and unexpected disk usage on Talos Linux nodes

Goal: Identify why Talos Linux nodes exhibit steady disk consumption over time despite no apparent workload growth, focusing on the containerd image garbage collection behavior. Constraints: Talos Linux uses an immutable root filesystem, so logs and temporary data are ephemeral; the containerd GC policy is disabled by default, leaving image cleanup to manual

garbage-collection

talos containerdTasadduq Burneyowner28K rep · 31 May 2023, 14:53 UTC

Editorial question88.6K views3,806 votes1 answer2,977 following

AI-generated

Lua 5.4 Generational GC: Tuning Pause and Step Parameters

Generational GC in Lua 5.4 Lua 5.4 adds a generational mode that must be enabled with collectgarbage('generational') . The mode changes how the collector ages objects and can alter the impact of the traditional pause and step settings. Unresolved Tuning Question When the generational collector is active, the relationship between pause and step and the result

garbage-collection

lua lua-5-4Tasadduq Burneyowner28K rep · 03 May 2022, 07:06 UTC