paperbot · PL 论文追踪

全部论文 待读 收藏

P2 SpecPMT: Speculative Logging for Resolving Crash Consistency Overhead of Persistent Memory

SpecPMT:用于消解持久内存崩溃一致性开销的推测式日志
ASPLOS Proceedings of the 28th ACM International Conference on Architectural Support for Programming Languages and Operating Systems, Volume 22023匹配度 1/10 · 该论文研究持久内存崩溃一致性与推测式日志,属于系统/体系结构中的运行时与内存管理,与用户关注的静态分析、LLM/Agent、浮点程序分析及贝叶斯程序分析均无直接关联。引用 13 inbox
Chencheng Ye, Yuanchao Xu, Xipeng Shen, Yan Sha, Xiaofei Liao, Hai Jin, Yan Solihin
crossref: 2026-09-12

AI 速览

一句话:提出推测式日志与推测式持久内存事务 SpecPMT,跳过大部分内存栅栏并提前记录数据值,把持久事务开销降至 10%。

崩溃一致性开销长期阻碍字节可寻址持久内存在实践中被采用:即使不断改进,持久事务仍带来 5.6 倍的性能下降,使持久内存成本过高。本文提出推测式日志(speculative logging),通过提前记录数据值来规避大部分内存栅栏,并降低数据持久化的开销。该技术支撑了一种新的持久事务模型——推测式持久内存事务(SpecPMT)。评估结果显示,SpecPMT 将持久事务的执行时间开销大幅降低到仅 10%,相比原先 5.6 倍的减速有明显改善,从而使持久内存在实际场景中更具可行性。

问题
字节可寻址持久内存中的崩溃一致性保障代价高昂,现有持久事务即使经过持续优化仍造成约 5.6 倍执行时间减速,阻碍其实际部署。
方法
提出推测式日志技术:提前记录数据值,从而省去大部分内存栅栏并降低数据持久化开销,并据此构造新的持久事务模型 SpecPMT。
评估
通过实验测量持久事务的执行时间开销,结果显示 SpecPMT 将该开销从 5.6 倍减速降至仅 10%。
原文摘要(Abstract)

Crash consistency overhead is a long-standing barrier to the adoption of byte-addressable persistent memory in practice. Despite continuous progress, persistent transactions for crash consistency still incur a 5.6X slowdown, making persistent memory prohibitively costly in practical settings. This paper introduces speculative logging, a new method that forgoes most memory fences and reduces data persistence overhead by logging data values early. This technique enables a novel persistent transaction model, speculatively persistent memory transactions (SpecPMT). Our evaluation shows that SpecPMT reduces the execution time overheads of persistent transactions substantially to just 10%.

链接与引用

DOI 原文 · PDF(开放获取) ·

BibTeX
@inproceedings{paperbot10041,
  title = {SpecPMT: Speculative Logging for Resolving Crash Consistency Overhead of Persistent Memory},
  author = {Chencheng Ye and Yuanchao Xu and Xipeng Shen and Yan Sha and Xiaofei Liao and Hai Jin and Yan Solihin},
  booktitle = {ASPLOS},
  year = {2023},
  doi = {10.1145/3575693.3575696}
}