Well Exchange 2013 lasted less than 12 hours here,
It just wants RAM!! - no matter how much I give it, it uses it all up and demands more!
When it doesn't get more it throws a temper tantrum and grinds not only itself to a halt but the entire Hyper-V environment!
Grr...
How much RAM have you given it? It says 8GB minimum having a quick read online.
One machine I had for Exchange 2010, ate 64GB RAM and demanded more. It is one of the biggest resource hogs known to man!
It was an 10GB when I gave up!
I thought it was supposed to be less RAM hungry than 2010 too. Our 2010 manages on 8GB, only a hundred or so users though.
Exchange is meant to use up all of your RAM (just like SQL Server).
Yet exchange 2003 was happy with a single server and 2GB
Yeah, I've noticed that however much RAM you have, exchange will just eat it.Originally Posted by Arthur
Exchange is meant to use up all of your RAM (just like SQL Server).
There's a bloody good reason why we avoid Exchange like the plague! 4GB on a (fairly crowded) VM and Zimbra doesn't even touch the sides! 2k accounts.
RAM is there to be used. What's the point in putting 64gb of RAM in a server if the majority is going to be unused?
As Arthur points out exchange will use all available RAM just like SQL. This is to relieve the requirements on disk speeds to enable virtualization. If you don't give fixed RAM allocation Hyper-V will over subscribe and bring down the whole box. Dynamic RAM is not supported with exchange for this reason.
We were meant to be having Exchange Server on 1 physical server with Sharepoint also. Sharepoint ended up going on another server.
Yea which is fine but it should also be able to live within its means. Ours does but it sounds like the ops install did not.Exchange is meant to use up all of your RAM (just like SQL Server).
I know that exchange and SQL and such systems all want decent specs, but MST of those systems run just fine in were specs such as my lab.
I mean, sccm 2012 wants way more than it currently gets but runs absolutely fine with 3GB and SQL runs fine with 4GB so expected exchange to do the same... but to max out 4GB right up to 10GB was just ridiculous..... 100% ram every time.....
It's how exchange works, it will attempt to load as much data as it can into RAM to avoid HDD IO calls, even with an SSD RAM is quicker
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks