innodb到现在还是mysql下最主要的支持事务的存储引擎,那么好,现在我们又多了一种选择了,
一种新的事务存储引擎 PBXT Storage Engine
以后mysql的主要存储引擎架构趋势已成:

这是原作者对这种存储引擎的总结:
先来看一下PBXT的架构吧:

AICD特性完整支持! 众多特性:
06年就开始有这么个东西了,始生之物,其形必丑,没错,开始的时候不是很完善,不过经过作者这2,3年的不断改进,
更新,已经有了巨大进步了。
作者的这张和INNODB的测试的性能图可以看得出差别了
作者的测试环境:
MySQL 5.1.30
8 core, 64-bit, Linux machine
with an SSD drive and a 5 warehouse DBT2 database.

从这个图的表现看出,随着引擎的版本越高,这存储引擎表现越来越好,
例如1.0.08的表现似乎有超越innodb的趋势。
以后要慢慢深入研究一下这个东东了
引擎下载:http://www.primebase.org/download/
快速指南:http://www.primebase.org/download/index.php#qg_source
白皮书: http://www.primebase.org/download/pbxt_white_paper.pdf
参考资料:
http://dev.mysql.com/tech-resources/articles/pbxt-storage-engine.html
http://pbxt.blogspot.com/
一种新的事务存储引擎 PBXT Storage Engine
以后mysql的主要存储引擎架构趋势已成:
这是原作者对这种存储引擎的总结:
Quotation
PrimeBase XT (PBXT) is a transactional storage engine for MySQL which can be loaded dynamically by the pluggable storage engine API of MySQL 5.1. It has been designed for modern, web-based, high concurrency environments. Full MVCC (multi-version concurrency control) support and a unique "write-once" strategy make PBXT particularly effective under heavy update loads.
先来看一下PBXT的架构吧:
AICD特性完整支持! 众多特性:
Quotation
1. MVCC: Multi-version concurrency control, enables reading without locking.
2. Transactional: support for BEGIN, COMMIT and ROLLBACK and recovery on startup.
3. ACID compliant: Atomic, Consistent, Isolated, Durable (once committed changes cannot be lost).
4. Row-level locking: updates use row-level locking allowing for maximum concurrency.
5. Deadlock detection: immediate notification if client processes are deadlocked.
6. Referential Integrity: foreign key support.
7. Write-once: PBXT avoids double-writes by using a log-based architecture.
8. BLOB streaming: In combination with the BLOB Streaming engine.
2. Transactional: support for BEGIN, COMMIT and ROLLBACK and recovery on startup.
3. ACID compliant: Atomic, Consistent, Isolated, Durable (once committed changes cannot be lost).
4. Row-level locking: updates use row-level locking allowing for maximum concurrency.
5. Deadlock detection: immediate notification if client processes are deadlocked.
6. Referential Integrity: foreign key support.
7. Write-once: PBXT avoids double-writes by using a log-based architecture.
8. BLOB streaming: In combination with the BLOB Streaming engine.
06年就开始有这么个东西了,始生之物,其形必丑,没错,开始的时候不是很完善,不过经过作者这2,3年的不断改进,
更新,已经有了巨大进步了。
作者的这张和INNODB的测试的性能图可以看得出差别了
作者的测试环境:
MySQL 5.1.30
8 core, 64-bit, Linux machine
with an SSD drive and a 5 warehouse DBT2 database.
从这个图的表现看出,随着引擎的版本越高,这存储引擎表现越来越好,
例如1.0.08的表现似乎有超越innodb的趋势。
以后要慢慢深入研究一下这个东东了
引擎下载:http://www.primebase.org/download/
快速指南:http://www.primebase.org/download/index.php#qg_source
白皮书: http://www.primebase.org/download/pbxt_white_paper.pdf
参考资料:
http://dev.mysql.com/tech-resources/articles/pbxt-storage-engine.html
http://pbxt.blogspot.com/
相关日志
Mysql replication Error "Slave_SQL_Running:No"
change mysql data directory
Sun陨落
mysql replication多源服务器下的auto_increment冲突问题
Mysql replication Error "Slave_SQL_Running:No"
change mysql data directory
Sun陨落
mysql replication多源服务器下的auto_increment冲突问题
作者:askwan@『AskWan』
地址:http://www.askwan.com/post/167/
可以转载,转载时请以链接形式注明作者和原始出处及本声明!
mysql replication多源服务器下的auto_increment冲突问题
遭遇 ORA-01102: cannot mount database in EXCLUSIVE mode

2009/04/28 13:57 | by











