TechEd: Exchange 2010 faster, more scalable than Exchange 2007

Microsoft Corp. said Monday that its upcoming Exchange Server 2010 software will be able to read and write e-mails to disk 70 per cent faster than Exchange 2007, despite the fact it uses the current same engine.

Last month, Microsoft released the public beta of Exchange 2010, which is due by year’s end. At the time, it unveiled a number of flashy end-user features designed to match or keep pace with Google Inc.’s Gmail.

At the Tech Ed conference in Los Angeles, a Microsoft developer detailed a handful of back-end improvements in Exchange Server 2010. All address performance and scalablity, which has long been a sore point for Exchange administrators and users, with Exchange’s Jet database engine taking much of the blame.

Several years ago, Microsoft announced a plan to move Exchange to a SQL Server-based database engine, but later abandoned it. The software maker’s road map for SQL Server and a complement of add-ons is more focused on business intelligence and data warehousing.

While keeping Jet for Exchange 2010, Microsoft changed its storage schema such that reading and writing mails to disk will be smoother and less bursty, according to Ross Smith IV, a senior technology architect for Microsoft.

That will result in a 70 per cent I/O improvement over Exchange 2007, and 90 per cent improvement over Exchange 2003, he said.

Exchange 2010 mailboxes will also be able to store up to 100,000 items per folder, up from 20,000 in Exchange 2007 and 5,000 in 2003, he said.

Exchange 2010 is even more role-based than prior versions. In Exchange 2003, servers running the software could be configured as either a front-end proxy or a mailbox server, which offloaded work from the core mailbox server.

In Exchange 2007, servers can be configured as one of 5 roles: hub transport, mailbox, unified messaging, edge transport and client access.

Exchange 2010 still has five roles. However, client access servers are being “beefed up,” such that they become a true middle-tier framework that handles all data rendering and conversion for both Outlook and Outlook Web Access, said Smith.

That will free up a mailbox server in Exchange 2010 to handle up to 120,000 active connections, versus just 12,000 or so in Exchange 2007, he said.

Mailbox servers will also now be able to fail over to another one within 30 seconds, compared to two minutes or more for Exchange Server 2007.

Another new feature called shadow redundancy will enable two copies of an e-mail message to be kept so that administrators do not need to run a RAID backup.

Some smaller companies and branch offices may run all of their Exchange 2010 roles on a single server with up to 16 processor cores. But most should run multiple servers, for safety reasons, he said.

“We would much rather see you scale out than scale up,” Smith said.

Servers performing client access duties need at least eight CPU cores and 8GB of RAM in Exchange 2010. Servers can have up to 12 cores, but more may lead slower performance due to “processor cross-talk,” he said.

Related Download
How Well Do You Know Your Apps? How to Implement a Continuous Application Monitoring Initiative Sponsor: HPE
How Well Do You Know Your Apps? How to Implement a Continuous Application Monitoring Initiative
Watch our insightful security webinar to learn more about how to implement a continuous application monitoring initiative.
Register Now