Metraipolis › archive › dc_a96f28abdb9d
Tide: Reclaiming Phased Memory in Agent MicroVMs — arXiv:2609.40082
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.40082
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-07T15:20:10.500Z
- SHA-256 of the archived text
13c99a6c1bc0dede32e8ee2a3af2d47a63df6b60927ef8b1bf12e88ff4e5bdf9- Stable URL of this page
https://metraipolis.com/documento/dc_a96f28abdb9d
How to cite
Tide: Reclaiming Phased Memory in Agent MicroVMs — arXiv:2609.40082 — arXiv (en), https://arxiv.org/abs/2609.40082 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_a96f28abdb9d (Metraipolis archive dc_a96f28abdb9d, sha256 13c99a6c1bc0dede32e8ee2a3af2d47a63df6b60927ef8b1bf12e88ff4e5bdf9)
BibTeX
@misc{dca96f28abdb9d,
title = {Tide: Reclaiming Phased Memory in Agent MicroVMs — arXiv:2609.40082},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.40082},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_a96f28abdb9d; sha256 13c99a6c1bc0dede32e8ee2a3af2d47a63df6b60927ef8b1bf12e88ff4e5bdf9},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.40082. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Cloud agents run each task in an isolated MicroVM. The trouble is the harness loop inside that guest: the harness is nearly idle while it waits on the model, then usage rises on a tool whose size is known only at run time, which complicates memory management from the host. Existing approaches infer reclaim targets from access frequency and memory footprint while the guest allocator places the idle harness and the short-lived tool on the same pages. Therefore, reclamation either selects the wrong pages, fixes on an incorrect capacity, or partially reclaims a huge page, splitting its transparent huge page. This paper proposes Tide, a proactive memory reclamation technique for agent MicroVMs. Our key insight is that the harness already knows each phase's memory intent (which memory, when, and whether its contents must survive), so the guest can report that intent as an exclusive guest-physical region for the host to reclaim directly. To realize this insight, we introduce an abstraction called arena and a set of user-space APIs for managing memory with exclusive intent; a guest-kernel allocator that groups exclusive allocations into huge-page-aligned extents; and a hypervisor extension that resolves those extents to host backing and applies the reported action, leaving guest capacity unchanged. Experiments on recorded agent trajectories show that Tide outperforms state-of-the-art mechanisms while incurring low overhead. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-10-01 in cs.OS). Categorie arXiv: Operating Systems (cs.OS). Pagina del lavoro: https://arxiv.org/abs/2609.40082 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-07T14:53:17.074Z dalla pagina https://arxiv.org/catchup/cs.OS/2026-10-01?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).