Process W3WP.EXE hogging memory

We have a Windows 2K8 R2 server with Exchange 2010 SP1 that has been running for about a year now.  The server has 16GB of memory and ample hard disk space.  The IIS worker process has suddenly been causing low memory conditions.  The "w3wp.exe" process in one instance is using over 1GB of memory.  Have to periodically reboot.  
Will moving to SP3 resolve this condition?  Have been somewhat apprehensive about installing.   Do not want to break Exchange at this point.

Appreciate any input!
WebccAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Frosty555Commented:
w3wp.exe consuming 1GB of memory sounds pretty typical to me, even on the low side. IIS is used heavily in the communication between Exchange Server and Outlook, so this doesn't seem out of the ordinary to me.

Where is your other 15GB of memory going to?

Exchange Server will automatically consume all of the available memory on the server for caching so it is normal to see the server almost entirely out of memory - Exchange will relinquish the memory if another process needs it down the road. If you're not having performance issues there probably isn't much to worry about.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WebccAuthor Commented:
Well the server crashed a couple of times and according to the logs it ran out of memory to continue processing.  The "Store.exe" process is using around 2G, but I think that's normal.  Did see a KB relating to this, but it seems to be with SP2 and we are still on SP1.  It has been stable since I posted this, Should I patch Exchange with SP3?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.