GitHub - xtellect/spaces: A high-performance C allocator with explicit heap regions, fragmentation control, and runtime tuning.

A high-performance C allocator with explicit heap regions, fragmentation control, and runtime tuning. - xtellect/spaces

Everything old is new again: memory optimization

At this point in history, AI sociopaths have purchased all the world's RAM in order to run their copyright infringement factories at full bl...

Anthropic Adds Auto Dream to Claude Code for Memory Cleanup

Anthropic began rolling out Auto Dream, a background sub-agent that consolidates Claude Code's memory files between sessions. The four-phase cycle fixes duplicates, stale dates, and contradictions that degraded auto-memory quality after 20+ sessions. The system prompt is already public on GitHub.

Agentenlog – KI-News + Praxis + Deep Dives

Wie KI‑Agenten wirklich funktionieren — News + Praxis + Deep Dives. Mehr als nur News: Tutorials, Analysen und Eindrücke aus der Agenten-Welt.

How OpenClaw's Memory System Actually Works

LLMs have no memory. OpenClaw builds the illusion of memory from files, conversation history, and retrieval — three subsystems working together. Here's how each one works, and where each one breaks.

Investing in Infrastructure: Meta’s Renewed Commitment to jemalloc

Meta recognizes the long-term benefits of jemalloc, a high-performance memory allocator, in its software infrastructure. We are renewing focus on jemalloc, aiming to reduce maintenance needs and mo…

The Scheduler | Internals for Interns

In the previous article we explored how Go’s memory allocator manages heap memory — grabbing large arenas from the OS, dividing them into spans and size classes, and using a three-level hierarchy (mcache, mcentral, mheap) to make most allocations lock-free. A key detail was that each P (processor) gets its own memory cache. But we never really explained what a P is, or how the runtime decides which goroutine runs on which thread. That’s the scheduler’s job, and that’s what we’re exploring today.

DOS Memory Management | OS/2 Museum