Exchange 2010 Database Compression
来源:互联网 发布:javascript垂直居中 编辑:程序博客网 时间:2024/06/10 13:07
One of the features of Exchange versions up to 2007 is Single Instance Storage (SIS). What SIS does is that it creates a single instance of messages sent to multiple recipients within the same database. Simply said, the first one gets a copy of the message in his or her mailbox, others get a referral to the message.
With the arrival of Exchange 2010 Microsoft made changes to the Extensible Storage Engine (ESE) .. again. Many of these changes are beneficiary to the performance of the system (read: less IOPS). For instance, Exchange 2010 uses larger pages and it orders database pages in the background. In an optimal situation this will result in an IOPS reduction of 70% versus Exchange 2007 (against Exchange 2003 a whopping 90%).
However, one of the victims of the new ESE is Single Instance Storage. This sounds worse than it is. Large (1 GB+) mailboxes are common nowadays, the maximum number of databases has increased and when looking at recovery times you are more likely to use multiple databases to reduce recovery times.
These developments also reduce the effectiveness of Single Instance Storage, which only works in a single database. In addition, the price of storage has dropped enormeously and focus these days is more on performance than on disk space.
Now before you think about getting additional storage space to counter the effects of SIS absence, I have good news. The new Exchange 2010 ESE engine has built-in storage compression. Certain parts of e-mail messages (headers, body) are stored in compressed format. Attachments are not compressed. Reason for not compressing attachments is that (de)compressing would be too CPU intensive (goodbye to performance improvements due to I/O reduction). Another reason I can think of is that it would be pointless to compress attachments as 90% of the attachments are probably already compressed (zip, docx, jpg).
First measurements show storage compression neutralizes the effects of SIS being gone. In fact, results are expected to be a lot better because storage compression doesn’t rely on messages being stored in the same database. Measurements also indicate overhead caused by (de)compression is equal or less than the amount of overhead required for the extra IOPS for fetching/storing uncompressed information.
For those interested, the algorithm used here is the same as in MAPI and DAG network traffic, i.e. XPRESS. This is a Microsoft implementation of the LZ77 algorithm. For more background information – or if you can’t sleep – check out the underlying RTF Extensions Specification.
- Exchange 2010 Database Compression
- Oracle Database Compression 2 - Advanced/OLTP Compression
- Oracle Database Compression 3 - Hybrid Columnar Compression
- Oracle Database Compression 1 - Basic Compression
- Exchange DAG(Database Availability Groups)
- Compression
- Table Compression Enhancements in Oracle Database 11g Release 1
- SAP SQL 压缩 Database compression for SQL Server
- Blackberry Exchange Mailbox Database 访问权限问题
- SQL SERVER BACKUP DATABASE 加快备份速度方法(压缩-Compression)
- SQL SERVER BACKUP DATABASE 加快备份速度方法(压缩-Compression)
- 聊聊Exchange 2010 的日志-Exchange 2010!
- Exchange 2003 迁移到 Exchange 2010
- Exchange 2010 Powershell 常用命令!
- Exchange 2010 SP2新功能
- Exchange 2010 共享邮箱
- Exchange 2010输入序列号
- exchange 2010 数据结构
- ACM日历题新版(界面修改+国际节日)(空)
- gerrit安装笔记
- oracle 增删改查基础操作 及rownum 和rowID 详解
- CC2014中国互联网版权保护行动计划启动
- 中国大陆开源镜像站汇总
- Exchange 2010 Database Compression
- 2014年3月14日注册CSDN博客
- 我的考研宏伟计划
- 修复Win7文件夹内左侧内容消失文件夹左移显示异常(图)
- 一句话说明设计模式——工厂模式
- 牛B的代码--97年Mekka ’97 4K Intro比赛
- 解决使用jquery esayUI是重复加载
- 2014城中春日牛津便鞋系列 IT的精英值得拥有
- 应用程序常驻系统