Sending, Receiving, and Notification Performance
In Outlook 2011, it could take a while to receive a message even if it were on an Exchange account. The reason is that Outlook was polling the server periodically for new messages.
Outlook 2016 does true push from the server, and as a result the time to notification of a received message, and the speed of meeting requests making their way through the process are significantly an issue. Together, these presented a feeling of a much more up to date, and snappy interface. Overall, we found Outlook 2016 to be about 5x faster in receiving messages than Outlook 2011.
Also, it isn’t just on the receiving side. Outlook 2016 sends emails a great deal faster as well — 15x faster.
Figure 9: Sending, Receiving, and Notification Performance
(shorter is faster)
- Page 1: Intro
- Page 2: Overview
- Page 3: Top-Level Results
- Page 4: Test Environment
- Page 5: Specific Testing
- Page 6: App Launch and Quit
- Page 7: Operations
- Page 8: Searching
- Page 9: CPU and Memory Footprint
- Page 10: Energy Footprint
- Page 11: User Interface Performance
- Page 12: Sending, Receiving, and Notification Performance
- Page 13: Sync Performance
- Page 14: Exchange vs. IMAP
- Page 15: Local Exchange Sync Performance
- Page 16: Local IMAP Sync Performance
- Page 17: Office 365 Sync Performance
- Page 18: Gmail Sync Performance
- Page 19: What about Mail.app?
- Page 20: From the Server Perspective
- Page 21: Conclusion