» Tag
memory-management
15 postsRust Stabilizes Core Allocator API for Box and Vec
Rust stabilizes the Allocator trait and custom-allocator support for Box and Vec, tightening safety rules and fixing key soundness bugs.
PostgreSQL and the Linux OOM Killer: A Safer Default
How strict Linux memory overcommit (vm.overcommit_memory=2) prevents OOM-killer-driven crashes in PostgreSQL, backed by a direct benchmark comparison.
Quantprobe Runs a 110B-Parameter LLM on a 16GB RAM 2016 Desktop
Quantprobe shows how careful memory-tier placement lets a 2016 desktop with 16GB RAM run a 110B-parameter LLM, validated with pre-registered predictions.
CommitBrief — AI code reviews, right in your terminal
A provider-agnostic, local-first CLI that reviews your staged changes, a historic range, or a whole GitHub pull request. Zero telemetry, no server. Free and open source.
commitbrief.comKernel devs review two LLM-assisted memory management patch sets
Two LLM-assisted Linux kernel patch sets—1GB huge page allocation and VM memory tracking—reveal how maintainers judge AI-assisted code.
Why Go Killed Memory Arenas — And What It Means for Its Future
Go shelved its Memory Arenas proposal over ecosystem fragmentation risks, capping its performance ceiling and squeezing its 'good enough' middle ground.
Knowledge and Memory Management: First Three Directions Finalized
Knowledge-and-Memory-Management locks in its memory store, graph adapter, and persistence contracts—API stays backward-compatible while internals are rewritten.
How to Export 1.2-Gigapixel Images on iPhone Without Memory Issues
Learn how to export 1.2-gigapixel images on your iPhone without running out of memory.
Knowledge-and-Memory-Management v0.0.2: Portable Agent Memory Release
v0.0.2 unifies web, video and article ingestion, adds automatic memory consolidation, and enables full portability via the $AGENT_HOME variable.
Why Rust services hold onto memory: glibc, jemalloc and munmap
A Rust service's RSS stayed flat after load tests. The cause wasn't a memory leak but glibc's arena-based allocator behavior; switching to jemalloc fixed it.
Allocating on the Stack
Go 1.25 and 1.26 enhance stack allocations, reducing garbage collector load and improving memory efficiency.