[InnoDB系列] - InnoDB VS PBXT实测
2008-07-25 15:43
627 查看
作/译者:叶金荣(Email:
),来源:http://imysql.cn,转载请注明作/译者和出处,并且不能用于商业用途,违者必究。
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的性能区别。
innodb:
pbxt:
本文出自 “MySQL中文网”博客 http://www.imysql.cn/
本文出自 “爱MySQL” 博客,转载请与作者联系!
),来源:http://imysql.cn,转载请注明作/译者和出处,并且不能用于商业用途,违者必究。
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 准备数据
本次测试分2部分进行,一部分是利用MySQL官方提供的 sql-bench 工具测试,另一部分采用 sysbench 做一个基准测试。本文出自 “MySQL中文网”博客 http://www.imysql.cn/
本文出自 “爱MySQL” 博客,转载请与作者联系!
相关文章推荐
- 实测Raid5 VS Raid1+0下的innodb性能
- 实测Raid5 VS Raid1+0下的innodb性能
- VS 2010 与 .NET 4 系列 - 目录
- [InnoDB系列] -- innodb表如何更快得到count(*)结果
- 【Visual Studio风格开发系列 - WinForm设计时异常】关于VS.NET中窗体设计器初始化控件引发的设计时异常
- VS,WCF(DotNet)常见错误处理系列(整理)
- 开始VS 2012 中LightSwitch系列的第2部分:感受关爱——定义数据关系
- MySQL系列:innodb引擎分析之内存管理
- 优化系列 | InnoDB引擎数据表压缩特性测试
- 优化系列 | MySQL 5.6.10 vs Percona 5.6.6之TPCCC性能测试
- VS 中配置使用Visual SVN系列 四:SVN Server配置和使用
- VC++6.0 VS 插件系列(绝对经典)
- 让人一用钟情的VS插件系列之一——Web Essentials(Web开发必备利器)
- 思考mysql内核之初级系列7---innodb的hash表实现(摘自老杨)
- 面试100题系列之8单词反转 VS HDU1062——text reverse
- mysql 开发进阶篇系列 18 MySQL Server(innodb_buffer_pool_size)
- 复制网页带来的行号问题,VS系列解决方式大放送!
- InnoDB vs MyISAM
- Win10 UWP开发系列:使用VS2015 Update2+ionic开发第一个Cordova App
- VS 2010 和 .NET 4 系列