AI & ML
Memory-Aware Keyframe Management for Dense Maps on Memory-Constrained Robots
arXiv cs.RO0 views
arXiv:2610.33574v1 Announce Type: new Abstract: Running a language model and a dense 3D map on one device means the two share one memory, and exceeding its limit is an out-of-memory failure. Map systems that keep a bounded working set bound it by a count of keyframes, but the memory one keyframe occupies varies widely with what it carries, so a count does not control what the working set occupies. The unit of admission is as poorly matched, since a radius around the pose, a fixed cell, or the graph neighbors of the last matched keyframe all move parts of the map that are not needed. We therefore propose two decisions. First, the memory the resident map uses is bounded directly, and the cost of every admission is known before any data is read, from per-keyframe resident sizes computed offline and carried with the map. Second, keyframes are admitted and released at a semantic spatial unit, the rooms and corridors of the building, so that the robot holds the zone it occupies together with the zone it is about to enter while the zones it has passed are released. Every admission measures the resident total, makes room, and only then reads, so the budget is never overshot. On two NVIDIA Jetson boards the budget holds in every run and the model gives up at most 0.8 percent of its throughput, whereas without it the operating system kills the model or the map. Under that budget, and over the environments evaluated, admission by semantic zone localizes 6-9 points more of the query frames than a geometric partition of matched zone count and about twice as much as the retrieval of RTAB-Map, at a lower ATE. Bounding memory lets the map and the model coexist, and moving the map in semantic zones makes the bounded map usable.
Source:https://arxiv.org/abs/2610.33574PreviousWorldFailBench: Do World Models Understand Policy Failures?NextHA-DiPO: Diffusion Policy Optimization for Heterogeneous Cooperative Transport
Related posts
When a PDF Export Turns Every Page Into a Picture, Define the Text Contract First
0dev.to Testing
Software Testing for Beginners: Why Working Code Is Not Always Correct Code
0dev.to Testing
I Graded 120 Agent Runs. Enforcement Bought the Paperwork, Not the Fix
0dev.to Testing
AI Agent Security Guide
0dev.to Kubernetes
Hydra v1: new DOI and the complete DOI registry (2026-11-02)
0dev.to OpenSource
Lorenz 1.2.3: AppImage AppStream metadata fix
0dev.to OpenSource