![]() ![]() There is a counter in performance monitor called "Processor Information(_Total)\% of Maximum Frequency". How do you know if this is happening? On a physical server the answer is easy. Even if you aren't using hardware based power management, just having the power plan set to the default "Balanced" can be enough to throttle the CPU power. You should allow the operating system to manage power and you should always use the "High performance" power plan in Windows. If hardware power management is an option, don't use it. For Exchange the guidance is straight forward. Now what if you were to find out that your 2.4GHz cores are only operating at 1.2GHz most of the time? That might make a difference in your reported CPU utilization. Everything looks great except the CPU utilization. You don't see any unusual client activity. You've ran the sizing numbers over and over and you should be closer to 55%. You have a server running at about 80% CPU throughout the work day consistently. So why is this a bad thing? Consider this. It saves power, lowers the electric bill, gives you a nice low carbon footprint, and makes vegetables taste good. On workstations and perhaps on certain servers this can be a good thing. Power management allows the hardware or the OS to, among other things, throttle power to the CPU and turn off an idle network card when it isn't in use. Power management sounds like a good thing, right? In many cases it is. I started losing count a while back of the number of high CPU cases I encountered that were caused by misconfigured power management. You can read more about the different versions of the. Future releases will contain even more improvements so be sure to always check for the latest available version. It should also be noted that 4.5.2 is the latest version as of the publishing of this blog post. You can save yourself a lot of trouble by upgrading to 4.5.2 as soon as possible, if you are not already there. We've seen more than a few of these in support. There have been multiple performance related fixes from version to version, some of which impact Exchange 2013 fairly heavily. However, I would strongly recommend that 4.5.2 be the default choice for any Exchange 2013 installation unless you have very specific reasons not to use it. All of these versions are supported on Exchange 2013. I will however touch on a few of the high points.Įxchange 2013 runs on version 4.5 of the. I'm not going to duplicate everything in the article here, I would suggest that you read if you are interested in this topic. This was actually the main motivation for a TechNet article we recently published called Exchange Server 2013 Sizing and Configuration Recommendations. Those of us that have worked enough performance issues start by following a list of things to check first. Therefore, I will not be covering Exchange 2010 in this post. NET Framework, and different implementation of. Some of these include completely different megacycle requirements, different versions of the. There are some fairly significant differences between Exchange 2010 and Exchange 2013 that change the best practices and troubleshooting methodology. High CPU issues across versions do have some things in common, however much of the data in this article is specific to Exchange 2013. Are you experiencing a problem, are databases inadequately balanced, or is the server just undersized? What about a 100% CPU condition? Does it happen for 10 seconds at a time or 10 minutes at a time? Does it only happen when clients first logon in the morning or after a failover? In this article I'll go into some common causes of high CPU utilization issues in Exchange 2013 and how to troubleshoot them.Īt this point I should note that this article is about Exchange 2013 specifically, not earlier versions. For example, say you consider ‘high’ to be 75% of CPU utilization during the day. ![]() What exactly is high? How long does it occur? When does it occur? All of these are questions that have to be answered before you can really start getting to the cause of the issue. "High CPU" can also be a bit of an ambiguous term as well. One of the most common performance issues we see are ones where the CPU is running higher than expected. This can manifest itself like anything from random client disconnects to database failovers or slow mobile device syncing. Part of the reason for that is the ambiguity of the term "Performance Issue". Few of them can be more difficult to troubleshoot than performance issues. In Exchange support we see a wide range of support issues. ![]()
0 Comments
Leave a Reply. |