>There have been many posts on the Exchange team blog about performance
>planning for Exchange but doesn't cover usage for OWA, IMAP and POP clients.
[quoted text clipped - 6 lines]
>I've heard of places putting up single Exchange 2000\2003 servers for
>15,000+ accounts. And using iSCSI and SATA drives for 10,000 users.
Your disk storage requirements are not necessarily going to change
unless of course you're in a hosting environment and haven't mentioned
that part.
Disk I/O will be less depending on whether or not your users are going
to be doing a send/receive every minute or so or, in the case of 5.5
users, hitting F5 for no good reason.
The sizing guidelines you will see assume mapi connections and assume
a certain level of concurrency with users but POP & OWA are different
beasts.
15k users on one server, probably, but not in a corporate environment
with large mailboxes and high concurrency. A hoster (Oliver may jump
in here) may well run servers in the high thousand users but they will
be behind slower bandwidth links and that affects the I/O profile of
client access.
Joe - 31 Jan 2007 19:08 GMT
This is for students at a University. I was going to base it on the light
user which was .11 IOPS. That would be about 2200 IOPS needed for the DB's.
The two servers would each be dual quad-core processors with 32GB. With 300
GB 10k FC, I would need about 18+ spindles per server.
>>There have been many posts on the Exchange team blog about performance
>>planning for Exchange but doesn't cover usage for OWA, IMAP and POP
[quoted text clipped - 23 lines]
> be behind slower bandwidth links and that affects the I/O profile of
> client access.