locked
Exchange 2007 SP1 memory usage RRS feed

  • Question

  • Hi

    We are running Exchange 2007 SP1 on a server with 18GB of memory. We are currently having performance problems in Outlook 2007 at our clients. We do not use cached mode, and when we change from inbox to the calendar or back it takes a while before it shows either the inbox or the calendar.

    I noticed that store.exe is using 10-11GB of memory and is constantly using 15-20% of CPU time. Is that normal? I have read that Exchange 2007 uses almost all available memory, but?


    /Lasse
    Friday, August 13, 2010 12:12 PM

Answers

  • You havent said how many users, what their IOPS/per user is estimated to be or if you sized your servers correctly per:

    http://msexchangeteam.com/archive/2007/07/05/445802.aspx

     

    But that CPU and RAM usage doesnt sound too far off the mark from normal. Cache mode is deisgned to mask latency issues from the client perspective and should really be used if users are experiencing issues.

    That said, I would go through the calculator to ensure you have sized your servers correctly and run ExBpa against the servers and ensure that any 3rd party products ( AV/Backups etc>) are configured correctly and not running during peak hours.

     

    • Proposed as answer by ZarkoC Friday, August 13, 2010 5:00 PM
    • Marked as answer by emma.yoyo Friday, August 20, 2010 2:57 AM
    Friday, August 13, 2010 12:45 PM
  • On Mon, 16 Aug 2010 12:33:13 +0000, LasseF wrote:
     
    >
    >
    >Monday was a good day regarding the performance issue with out Exchange server until around 2pm (30 minutes ago!). I checked earlier today, when everything was working perfectly and the Store.exe was using 0% CPU time, now after 2pm when the problem has returned it is using 15-25% CPU time.
    >
    >I am a bit new to Exchange 2007, but is there any maintenance schedules or something like it that might occur in the middle of the day? I have checked everything and can't find anything that should cause it.
    >
    >Is it possible to se how many threads the users have through the shell?
     
    You want to be using performance monitor to examine your problem . . .
    at least until you discover what's casuing things to slow down.
     
    Grab a copy of PerfWiz
    (http://blogs.technet.com/b/mikelag/archive/2010/07/09/exchange-2007-2010-performance-data-collection-script.aspx)
    and a copy of PAL (http://pal.codeplex.com/) and a copy of Log Parser
    2.2
    (http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&DisplayLang=en)
    and a copy MS Web Components
    (http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76)
    and run the data collection during the day. Then run PAL on the
    collected data and see if there are problem areas. Once you discover
    WHAT the problem is you start to address HOW to deal with it.
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by emma.yoyo Friday, August 20, 2010 2:57 AM
    Tuesday, August 17, 2010 2:31 AM
  • Hi Lasse,

     Currently your Exchange  Hardware configure are  sure to satisfy your Exchange Application requirement ,

    As suggestion as below:

    1,Check your outlook 2007 Version ,please upgrade to outlook 2007 sp2 as soon as possible

    2,check your all outlook client whether have same issues

    3,make use of EXMOM Tool to monitor your Outlook MAPI Clients ,


    Steve Xu
    • Marked as answer by emma.yoyo Friday, August 20, 2010 2:58 AM
    Tuesday, August 17, 2010 3:00 AM

All replies

  • You havent said how many users, what their IOPS/per user is estimated to be or if you sized your servers correctly per:

    http://msexchangeteam.com/archive/2007/07/05/445802.aspx

     

    But that CPU and RAM usage doesnt sound too far off the mark from normal. Cache mode is deisgned to mask latency issues from the client perspective and should really be used if users are experiencing issues.

    That said, I would go through the calculator to ensure you have sized your servers correctly and run ExBpa against the servers and ensure that any 3rd party products ( AV/Backups etc>) are configured correctly and not running during peak hours.

     

    • Proposed as answer by ZarkoC Friday, August 13, 2010 5:00 PM
    • Marked as answer by emma.yoyo Friday, August 20, 2010 2:57 AM
    Friday, August 13, 2010 12:45 PM
  • Hi Andy

    We have 110 users. I have no idea how IOPS/per user i estimated. I am new here and haven't uncovered everything yet :-)

    I agree that it doesn't sound too far of the mark from normal, but wasn't sure.

    I will go through the calculator later and run the ExBpa and see what the result is.


    /Lasse
    Monday, August 16, 2010 6:45 AM
  • Monday was a good day regarding the performance issue with out Exchange server until around 2pm (30 minutes ago!). I checked earlier today, when everything was working perfectly and the Store.exe was using 0% CPU time, now after 2pm when the problem has returned it is using 15-25% CPU time.

    I am a bit new to Exchange 2007, but is there any maintenance schedules or something like it that might occur in the middle of the day? I have checked everything and can't find anything that should cause it.

    Is it possible to se how many threads the users have through the shell?


    /Lasse
    Monday, August 16, 2010 12:33 PM
  • On Mon, 16 Aug 2010 12:33:13 +0000, LasseF wrote:
     
    >
    >
    >Monday was a good day regarding the performance issue with out Exchange server until around 2pm (30 minutes ago!). I checked earlier today, when everything was working perfectly and the Store.exe was using 0% CPU time, now after 2pm when the problem has returned it is using 15-25% CPU time.
    >
    >I am a bit new to Exchange 2007, but is there any maintenance schedules or something like it that might occur in the middle of the day? I have checked everything and can't find anything that should cause it.
    >
    >Is it possible to se how many threads the users have through the shell?
     
    You want to be using performance monitor to examine your problem . . .
    at least until you discover what's casuing things to slow down.
     
    Grab a copy of PerfWiz
    (http://blogs.technet.com/b/mikelag/archive/2010/07/09/exchange-2007-2010-performance-data-collection-script.aspx)
    and a copy of PAL (http://pal.codeplex.com/) and a copy of Log Parser
    2.2
    (http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&DisplayLang=en)
    and a copy MS Web Components
    (http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76)
    and run the data collection during the day. Then run PAL on the
    collected data and see if there are problem areas. Once you discover
    WHAT the problem is you start to address HOW to deal with it.
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Marked as answer by emma.yoyo Friday, August 20, 2010 2:57 AM
    Tuesday, August 17, 2010 2:31 AM
  • Hi Lasse,

     Currently your Exchange  Hardware configure are  sure to satisfy your Exchange Application requirement ,

    As suggestion as below:

    1,Check your outlook 2007 Version ,please upgrade to outlook 2007 sp2 as soon as possible

    2,check your all outlook client whether have same issues

    3,make use of EXMOM Tool to monitor your Outlook MAPI Clients ,


    Steve Xu
    • Marked as answer by emma.yoyo Friday, August 20, 2010 2:58 AM
    Tuesday, August 17, 2010 3:00 AM