So we have been chugging along fine since Feb 2 2014. 

I performed a migration from 2010 from the UK to the US doing "incremental" mailbox moves. (get in contact with me if you want to know how. But we moved 400 Mailboxes averaging at 2gb a piece from the UK to the US, over the transcontinental link. & then the weekend of the final, had everyone & everything done by the end of the cutover weekend)

Any woot.

So I applied the 2013 SP1 a few weeks back, & have intermitantly been alerted to the memory spiking over 95%. For me (and for any exchange admin) when i get those types of alerts i drop everything & run to the nearest PC to see what is going on.

Now the first & second time, it was an issue with logs filling up the drives, & my clean log script not running to remove any logs older than 30 days. But since then it has been legitimate 95%+ memory usage. 

For the most part its been 95-97 max, with 1 or 2 times hitting 98. After some time, the memory does drop back down to 94.

this is ....umm "fine" however it is becoming a nuisance, since most of the time it corrects itself. What i dont want to happen is get into the groove of saying "ah bah! its nothing" & letting it go.

the server has 16gb of memory in it, it is the Mailbox server (CAS /Frontend is on a seperate server)

below is a screen shot, so i know the Storeworker grabs whatever it feels like grabbing, however it does NOT EVER release memory.  I also see the NodeRunner.exe (2 of them)  is always around 900 almost a MB

now if i could somehow get the first 2 Storeworkers to drop down to 900ish, then that should alleviate my memory issues. 

what I am m looking for is some type of "magic bullet" to put my memory issues at ease..

• Edited by Steve_Lindsey 15 hours 8 minutes ago

I guess i should have also said that memory was fine pre-SP1

Hi,

The behavior you see on the mailbox servers for store.exe is completely normal. This is in order to allocate as much data in memory address space as possible, so that each user experience great performance in their Outlook clients. If another process should need the more memory, the Exchange store.exe process will released it as required. This is by design.

And,NodeRunner is part of Microsoft`s new Exchange search system other wast known as FAST search system. When you see noderunner.exe running it is going through all your email data stores and emails spidering and indexing all emails so that when users run a search in outlook or OWA, the results are returned in super fast time.

You will mainly see this process running quite intensiveness after you have either just installed or migrated to Exchange 2013 as it will obviously be indexing quite a lot of mail you have just imported. If you must stop the services as your system is running slow you can do this by stopping the Microsoft Exchange Search Host Controller service. When you restart that service the indexing will continue until it has completed.

It is recommend that when designing an Exchange 2013 solution that you reserve 15% of memory for this particular process.

Here is an similar thread for your reference:

http://social.technet.microsoft.com/Forums/exchange/en-US/4c14eaec-ce89-4da0-bf23-22fe029d1b4d/noderunnerexe-and-memory-use

Hope this helps!

Thanks.