Over the past decade, we have witnessed a dramatic evolution in main-memory capacity and multi-core parallelism of server hardware. To leverage this hardware potential, multi-core in-memory OLTP database systems have been extensively re-designed. The core objective of this re-design has been scaling up sequential execution of OLTP transactions, wherein alternative database architectures have been explored to eliminate system bottlenecks and overheads impeding inter-transaction parallelism to fully manifest. However, intra-transaction parallelism has been largely ignored by this previous work. We conjecture this situation to have developed because OLTP workloads are sometimes deemed to have far too little intra-transactional parallelism and, even when this kind of parallelism is available, program analyses to recognize it in arbitrary stored procedures are considered too brittle to be used as a general tool. Recently, however, a new concept of actor-relational database systems has been proposed, raising hopes that application developers can specify intra-transaction parallelism by modeling database applications as communicating actors. In this scenario, a natural question is whether an actor-relational database system with an asynchronous programming model can adequately expose the intra-transaction parallelism available in application logic to modern multi-core hardware. Towards that aim, we conduct in this paper an experimental evaluation of the factors that affect intra-transaction parallelism in the prototype actor-relational database system REACTDB, with an OLTP application designed with task-level parallelism in mind, and with the system running on a multi-core machine.
翻译:过去十年来,我们目睹了服务器硬件主模容量和多核心平行功能的急剧演变。为了发挥这一硬件潜力,我们广泛重新设计了多核心的平行OLTP数据库系统。这一重新设计的核心目标是扩大连续执行OLTP交易,探索了替代数据库结构以消除系统瓶颈和阻碍跨贸易平行的间接费用,以便充分显示。然而,此前的这项工作在很大程度上忽视了交易内部的平行关系。我们推测这种情况之所以有所发展,是因为人们有时认为OLTP的工作量太少,而且即使在存在这种平行关系的情况下,也广泛设计了多核心的OLTP数据库系统。在任意储存程序上承认它的程序分析被认为太小,无法用作一般工具。然而,最近提出了一个新的核心关系数据库系统概念,使应用程序开发者能够通过模拟数据库应用来说明内部平行关系,将数据库应用程序作为行为者进行交流。在这个假设中,一个自然的问题是,在内部关系数据库应用中,是否设计了一种动态的系统-关系应用,将一个动态的逻辑-直径直线数据系统与一个动态的逻辑-直径直径的逻辑-直径数据系统-直径对一个可操作的系统进行充分评价。