[InnoDB系列] - InnoDB VS PBXT實測

作/譯者：葉金榮（email:

），來源：http://imysql.cn，轉載請注明作/譯者和出處，并且不能用于商業用途，違者必究。

1、前言

pbxt 是 primebase 公司推出的mysql插件引擎，其功能和 innodb 類似，主要特性如下：

<b>mvcc support:</b>

mvcc stands for multi-version concurrency control. mvcc allows reading the database without locking.

<b>fully acid complient:</b>

this means that transactionally safe, and able to handle multiple concurrent transactions.

<b>row-level locking:</b>

when updating, pbxt uses row-level locking. row-level locking is also used during select for update.

<b>fast rollback and recovery:</b>

pbxt

uses a specialized method to identify garbage which makes "undo"

unncessary. this make both rollback of transactions and recovery after

restart very fast.

<b>deadlock detection:</b>

pbxt identifies all kinds of deadlocks immediately.

<b>write-once:</b>

uses a log-based storage which makes it possible to write transactional

data directly to the database, without first being writen to the

transaction log.

<b>referential integrity</b>:

pbxt supports foreign key definitions, including cascaded updates and deletes.

<b>blob streaming</b>:

in combination with the blob streaming engine pbxt can stream binary and media directly in and out of the database.

本次我們來實際對比測試下innodb和pbxt的性能差別。

2、準備

pbxt 和 innodb 主要配置參數如下：

innodb:

pbxt:

本次測試分2部分進行，一部分是利用mysql官方提供的 sql-bench 工具測試，另一部分采用 sysbench 做一個基準測試。

本文出自 “mysql中文網”部落格 http://www.imysql.cn/