arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2009.11558cs.DB
收藏

基于CCBench(扩展版)的内存数据库并发控制协议分析

An Analysis of Concurrency Control Protocols for In-Memory Databases with CCBench (Extended Version)

Takayuki Tanabe, Takashi Hoshino, Hideyuki Kawashima, Jun Nemoto, Masahiro Tanaka, Osamu Tatebe

摘要:

本文介绍了另一个并发控制分析平台CCBench。CCBench支持七种协议(Silo、TicToc、MOCC、Cicada、SI、带无锁存SSN的SI、2PL)和七种通用优化方法,并支持七种工作负载参数的配置。我们使用各种工作负载参数和线程数224分析了协议和优化方法。以前的研究集中在线程可伸缩性,并没有探索这里分析的空间。我们根据三个性能因素对优化方法进行了分类:CPU缓存,冲突延迟和版本生命周期。使用CCBench和224个线程进行分析,产生了六个见解。(I1)乐观并发控制协议在只读工作负载中的性能会随着基数的增加而迅速下降,即使没有L3缓存未命中。(I2)通过使用不可见的读取优化,Silo可以在某些写密集型工作负载上优于TicToc。(I3)处理冲突的两种方法(等待和不等待)的有效性取决于情况。(I4)如果发生并发事务中断,OCC将读取同一条记录两次或更多次,这可以提高性能。(I5)混合使用不同的实现不适合进行深入分析。(I6)如果工作负载中混入了单个长事务,即使是最先进的垃圾回收方法也无法提高多版本协议的性能。在I4的基础上,我们定义了读阶段扩展优化,其中在读阶段中添加人工延迟。在I6的基础上,我们定义了积极的垃圾回收优化,其中甚至收集可见的版本。CCBench的代码和本文中的所有数据都可以在GitHub上在线获得。

英文摘要:

This paper presents yet another concurrency control analysis platform, CCBench. CCBench supports seven protocols (Silo, TicToc, MOCC, Cicada, SI, SI with latch-free SSN, 2PL) and seven versatile optimization methods and enables the configuration of seven workload parameters. We analyzed the protocols and optimization methods using various workload parameters and a thread count of 224. Previous studies focused on thread scalability and did not explore the space analyzed here. We classified the optimization methods on the basis of three performance factors: CPU cache, delay on conflict, and version lifetime. Analyses using CCBench and 224 threads, produced six insights. (I1) The performance of optimistic concurrency control protocol for a read only workload rapidly degrades as cardinality increases even without L3 cache misses. (I2) Silo can outperform TicToc for some write-intensive workloads by using invisible reads optimization. (I3) The effectiveness of two approaches to coping with conflict (wait and no-wait) depends on the situation. (I4) OCC reads the same record two or more times if a concurrent transaction interruption occurs, which can improve performance. (I5) Mixing different implementations is inappropriate for deep analysis. (I6) Even a state-of-the-art garbage collection method cannot improve the performance of multi-version protocols if there is a single long transaction mixed into the workload. On the basis of I4, we defined the read phase extension optimization in which an artificial delay is added to the read phase. On the basis of I6, we defined the aggressive garbage collection optimization in which even visible versions are collected. The code for CCBench and all the data in this paper are available online at GitHub.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑