Can you say Memory Leak (Full Version)

All Forums >> [Microsoft Exchange 2007] >> General



Message

invitro -> Can you say Memory Leak (9.Feb.2007 2:35:55 PM)

I have been running 50 users on EX07, for a few weeks now. There seems to be a lot of memory that has gone unaccounted for. This is the only app on the box, so I figure we need a patch pretty soon.



Henrik Walther -> RE: Can you say Memory Leak (10.Feb.2007 4:16:10 AM)

You need to provide much more detailed information about this potential memory leak, before it can justify for a patch? [8D]



invitro -> RE: Can you say Memory Leak (21.Feb.2007 1:55:13 PM)

I am looking to see if anyone else is seeing this problem. I note the memory leak because

1. Exchange is the only software on the machine.
2. The Commited Memory measures 5GB
3. Task Manager measures only 3GB.

This would lead one to believe that some process is not deallocating memory properly. Since Exchange 2007 and Server 2003 R2 are the only software on the machine, it would be reasonable to assume the new software is the culprit.

Has anyone else seen this?



rogblanton -> RE: Can you say Memory Leak (11.May2007 3:18:43 PM)

I have an exchange 2007 server with 400 users running on a high end dell server and the page file usage has gone through the roof.

Has anyone else seen this?



rporter -> RE: Can you say Memory Leak (23.May2007 9:40:22 PM)

I just recently completed two Transitions to Exchange 2007, and I am experiencing the same issue on both of them.  It also appears that JimAdkins is experiencing the same issue:  http://forums.msexchange.org/m_1800441081/mpage_1/tm.htm.

My two situations started out the same way: 
 
(1)    On one, we started with 4GB of RAM and initially saw 6GB page file usage.  We upped the RAM to 8GB and page file usage went up to over 7GB.  We initially thought that the issue was Symantec’s Mail Security for Exchange product, however we found that even if Symantec was completely disabled page file usage would slowly but surely grow to around 7GB or higher.
 
(2)    On the other new Exchange 2007 transition, we initially had just the CAS and HUB roles installed.  In this configuration, there were no noticeable issues.  (Everything ran perfectly).  As soon as we installed the Mailbox role and moved some mailboxes performance became dismal at best and the page file shot up to over 6GB
 
With both instances, a reboot or restarting of the MSExchangeIS service reduces the Page File usage to an acceptable level, only to grow over time. 
 
I am continuing to troubleshoot the issue, and if I find an answer before one is posted here, I will definitely share.
Ryan



JimAdkins -> RE: Can you say Memory Leak (24.May2007 7:33:09 PM)

[image]http://djx86.com/exchange1.jpg[/image]

9GB of RAM.

[image]http://djx86.com/exchange2.jpg[/image]

12GB physical, and almost 14GB page file. This server should not be having these kinds of problems. There should be a way to optimize this. MS!!! HELP!!!

-Jim



ctohang -> RE: Can you say Memory Leak (26.May2007 1:46:15 PM)

I got the same problem with you, I setup a testing server to serve a few client for UAT test. I install addition 4GB Ram for the server, but the edge transport service use more memory than before (about 3.5 GB), I think it si the bug for the exchange 2007, right?
May I know How can report this bug to MS?
Thanks!



BeTaCam -> RE: Can you say Memory Leak (28.May2007 2:46:18 AM)

This is not an issue, but the way exchange 2007 works. If you recollect, the ESE Engine cache was 300 MB in Exchange 2003. This could be increased to a maximum of 896 Mb by whacking the /3GB switch.
 
 
In exchange 2007, the cache size is in multiples of 512 MB. However there is no maximum limit on the memory which can be grabbed for the cache, resulting in lesser disk I/O.
 
The Exchange 2007 consumes available memory. However if there be a thread or application which requires memory, Exchange will release the memory.
 
In short, this is not a memory leak, just that it consumes memory.
 
HTH
 
/BC



JimAdkins -> RE: Can you say Memory Leak (6.Jun.2007 7:56:06 PM)

Ok, I can understand if 2007 was written to use all available memory, but in my case, it's not only using all available memory but it is also paging 2GB. My total system memory is 12GB and it is using 14GB. Why would it page 2GB?

It's not like the server can't handle it. I haven't had any problems with 2007 except for this. It's just concerning when your email server take 3 minutes for you to remote desktop into. It's so slow I wouldn't know it was on without all the blinking lights.

My small 50 person company shelled out around 5 grand for the new server and all the RAM to put 2007 on, and it's hard when your IT director asks you why your brand new email server is so unresponsive.

-Jim



mulderlr -> RE: Can you say Memory Leak (7.Jun.2007 11:36:44 AM)

I agree with Jim.  Furthermore, I don't understand what makes caching a database until it runs performance of the server into the ground a good idea.  The other reasons this is bad is in virtualization.  Even if for testing (ex03 was supported under virtualization and ex07 will be if M$ ever fixes RAM usage) the impact on sibling VM's running on the same hardware as exchange which is busy gobbling up RAM and SWAP space for no real reason is beyond any reasonable person's comprehension.  This is a bug, exchange 2007 RAM usage is a problem - it's broken quite frankly - and it needs to be fixed.  Even MS SQL server provides a way to restrict RAM usage so it doesn't run away with the machine, but yet, Microsoft developers thought it would be a good idea to not include such a feature in exchange 2007? 

How are you supposed to run other software on this box?  Yes other software that you need for exchange such as, IIS for OWA, Terminal Services for administration, Exchange Management Console, etc.  It all causes even more swapping and more waiting!  We want a fix!



JimAdkins -> RE: Can you say Memory Leak (7.Jun.2007 5:13:16 PM)

quote:

ORIGINAL: mulderlr
Even MS SQL server provides a way to restrict RAM usage so it doesn't run away with the machine, but yet, Microsoft developers thought it would be a good idea to not include such a feature in exchange 2007? 


This was the first thing I thought of when I first started playing with our setup. I thought there must be a way to fine tune the RAM like in SQL. After doing some searching I could find no answers for what was happeneing. This is just really starting to annoy me.

Thanks for the support mulderlr!



BeTaCam -> RE: Can you say Memory Leak (8.Jun.2007 2:16:51 AM)

Well,[8|]
 
The 2 GB is reserved for the OS, hence a paging file is 2 Gigs. ( Thumb rule for memory sizing says, 2 GB for OS + X Mb per user).
 
The cache is high, so that the I/O on the disk is reduced. In case you want to restrict this to a threshold, you will have to use the MsExchESEParamCacheSizeMax key using ADSI Edit. ( you have to represent the max memory in multiples of 8).
 
I have deployed enough and more Exchange systems with 16GB and > than 16 GB. I have not seen any issue in the system releasing memory on demand by any application thread. ( backup, Antivirus, Antispam and etc etc..)
 
Q: If it hogs memory, has the performance degraded ? I am sure the answer is no. :)

Hth
 
BC[:D]



Belt -> RE: Can you say Memory Leak (11.Jun.2007 10:09:52 AM)

I have the same problem, and yes, when an app uses up all ram, performance degrades.

after a clean reboot, the serve rworks ok, until E2007 starts to gobble up all ram, and then starts swapping.

if the "ram release" would work, then it would be no problem, but when it takes 10s to open any window thanks to any request not finding ram and having to swap(besides killing the HD I/O), then the product is broken.

i'll try that ADSI edit thing and kill all the cache, it makes no sense



JimAdkins -> RE: Can you say Memory Leak (15.Jun.2007 1:12:21 PM)

quote:

Q: If it hogs memory, has the performance degraded ? I am sure the answer is no. :)


Actually, the answer is yes. Sometimes the performance sucks for about 5-10 minutes. I have to sit there and wait. I have initiated a remote desktop connection to the server and had it take 10 minutes before anything comes up. My connection will time out before I can even enter a password. I will do this a couple of times before it comes up and let's me enter a password. If I am already logged in and have been logged in for a long time and EX2007 has gobbled all the memory, I can open the exchange console and go get a cup of hot chocolate before it will come up.

Other times this is not the case. It will not take 10 minutes but only 1-2 minutes. BUT, it still takes a ridiculous amount of time to interact with the machine. If I have someone waiting for an email restore, and it takes me 10 minutes just to get into the machine, that doesn't inspire lots of confidence in the email or exchange 2007 system. When I have my CIO waiting for me to create a user, he starts to wonder why this new beefed up server that we spent a lot of money on will not come up in a timely manner.

-JimAdkins

Edit: I found this article for changing the msExchESEParamCacheSizeMax property.

http://support.microsoft.com/kb/815372

Is this the correct place? Is it the same as it was in 2003? Also, your multiples of 8, is that 8=1GB of RAM? or is it 8=1Byte of RAM? If I wanted to allow only 8GB of RAM would I put 64 (8x8GB) in here?

Thanks.



DrShinder -> RE: Can you say Memory Leak (16.Jun.2007 11:13:03 AM)

Is guess that's why they expect you to use Gonad or PowerHell to admin the dreaded thing -- there's not enough memory left to run the Exchange Management Console! [;)]



BeTaCam -> RE: Can you say Memory Leak (18.Jun.2007 3:05:37 AM)

Hi Jim.
 
The entries should be as follows.(bytes)
 
8 GB = 8 * [(1024*1024)/8] = 1048576
 
Steps
-----------------------------------------------------------------------------------------------
Start ADSI Edit. Locate  Configuration/Services/Microsoft Exchange/Your organization/Administrative Groups/................................./Servers/Server name/Information Store.
Right-click Information Store click properties.Under the list of Attributes, scroll down and select msExchESEParamCacheSizeMax.
change the value to 1048576 (Equivalent to 8 GB).
--------------------------------------------------------------------------------
 
Could you also please check these out.
 
1. The setting on your NIC, set it to Full Duplex. If you have an intelligent switch, then check the port which connects to that of the Exchange 2007 servers and the GC's and set them to Full Duplex ( and not auto-negotiate).
 
2. Check the page file settings. You'd need a minimum of 10 Gigs if you are leveraging a server with 8 GB physical memory. ( Memory + 2 Gb) * 1.5, should be the max if i am not mistaken.
 
Hth
 
/BC.



MarKiN -> RE: Can you say Memory Leak (18.Jul.2007 12:53:13 PM)

Iīve got th same problem. I donīt think that "itīs normally".

Yesterday, I took in production a new server E2K7, with 12Gb of Database and 30 Mailbox. Itīs the start of a big migration.

Server has 4Gb RAM and today another 2Gb more. 2Gb Pag file.

The E2K7 is in a new domain, new enviroment, new mailbox. Only import important mails by Outlook.

When I finish to import mails, E2K7 used RAM about 3Gb. Today, early morning, used 5.5Gb. Nobody has used during the night.

I restarted to add memory, and used 2.4Gb. Normally. Passed 4 hours, it used 3.7Gb. Store.exe, take a lot of memory, donīt stop. But only 8 or 9 persons used the E2K7.

What happened?I donīt think that itīs normally. I suposed the same problems of all Exchange versions. I need a tipycall MS hotfix....

P.D: not valid for me, add space to the Pagefile...itīs a bad hotfix...

Regards



dvord -> RE: Can you say Memory Leak (24.Sep.2007 2:50:13 PM)

I gotta dredge up this oldie 'cause I'm getting a potential memory leak as well. 

I know Exchange gobbles up memory, and I can deal with that.  I can't deal with being unable to run commands like "get-mailboxstatistics username"  If I execute this command while my system is beset upon by Exchange 2007 database gluttony, there is no response for that command. 

Image name: store.exe
CPU:  25
Mem Usage: 2,306,068k
VM Size:  2,555,448k
I/O Writes: 190,925
I/O Write Bytes:  3,173,401,632

I thought I/O Write Bytes was significant, especially considering the Mailbox and Public Folder stores on disk don't even exceed 30 GB together.

By restarting the store service I can get things to operate properly but only for some random amount of time.  HELP!?!



dvord -> RE: Can you say Memory Leak (19.Oct.2007 7:42:44 PM)

Rollup 4 solved my problems.



tadduci -> RE: Can you say Memory Leak (6.Dec.2007 2:30:29 PM)

Hello,
I am also having a problem with Exchange 2007 sp1 std. I have the Symantec Information Foundation Assistant running (mail security) and I see that after 2 weeks or so the system starts to act up with the transport connector to recieve email. Then the mail security product acts up and forces me to restart to resolve the error.

After a restart the system is perfect for a little while.
I have heard people discuss the chimney, the network card drivers, the duplex settings on the nic and what other products are installed.

It is amazing to me that I have to worry more about the random acting up of this server compared to the Exchange 2003 product that I migrated from. 64bit has done nothing for me with respect to Exchange. This product is not more stable than Exchange 2003 in its current form.

I have applied the hotfix that Exchange 2007 sp1 requests and that has not helped me any.



Page: [1] 2   next >   >>