1、前言
PBXT 是
PrimeBase 公司推出的MySQL插件引擎，其功能和
InnoDB 类似，主要特性如下：
- MVCC Support:
MVCC stands for Multi-version Concurrency Control. MVCC allows reading the database without locking. - Fully ACID complient:
This means that transactionally safe, and able to handle multiple concurrent transactions. - Row-level locking:
When updating, PBXT uses row-level locking. Row-level locking is also used during SELECT FOR UPDATE. - Fast Rollback and Recovery:
PBXT
uses a specialized method to identify garbage which makes "undo"
unncessary. This make both rollback of transactions and recovery after
restart very fast. - Deadlock Detection:
PBXT identifies all kinds of deadlocks immediately. - Write-once:
PBXT
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. - Referential Integrity:
PBXT supports foreign key definitions, including cascaded updates and deletes. - BLOB streaming:
In combination with the BLOB Streaming engine PBXT can stream binary and media directly in and out of the database.
本次我们来实际对比测试下InnoDB和PBXT的性能区别。
2、准备
2.1 配置
PBXT 和
InnoDB 主要配置参数如下：
innodb:
innodb_buffer_pool_size = 6G innodb_data_file_path = ibdata1:1024M:autoextend innodb_thread_concurrency = 8 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 16M innodb_log_file_size = 256M innodb_log_files_in_group = 3 innodb_max_dirty_pages_pct = 90 innodb_file_per_table
pbxt:
pbxt_checkpoint_frequency = 28MB pbxt_data_file_grow_size = 8MB pbxt_data_log_threshold = 128MB pbxt_garbage_threshold = 50 pbxt_index_cache_size = 2G pbxt_log_buffer_size = 2M pbxt_log_cache_size = 16MB pbxt_log_file_count = 3 pbxt_log_file_threshold = 128MB pbxt_record_cache_size = 4G pbxt_row_file_grow_size = 1M pbxt_transaction_buffer_size = 32MB
2.2 准备数据
本文转自叶金荣51CTO博客，原文链接：http://blog.51cto.com/imysql/308827，如需转载请自行联系原作者
