Creating Server Performance Baselines

Here’re some tips to create a one-stop shop for server performance baselines. So what exactly’s a baseline? Simply put, a baseline is a picture of how your server normally operates. Having a baseline is incredibly useful you’re doing capacity planning, performance-related troubleshooting, or even disaster recovery planning. Now, a good server baseline encompasses far more […]

Here’re some tips to create a one-stop shop for server performance baselines. So what exactly’s a baseline? Simply put, a baseline is a picture of how your server normally operates. Having a baseline is incredibly useful you’re doing capacity planning, performance-related troubleshooting, or even disaster recovery planning. Now, a good server baseline encompasses far more than just running Performance Monitor for couple of hours and then calling it a day. All tips below can be implemented using Microsoft tools that either come with server or are free to download.

10. One Baseline simply won’t do: OK, you’re already thinking … what? What’re you talking about? Server Performance is affected by time. Think about it – Monday mornings (well, probably every morning) at 9:00 am are probably when your domain controllers’re busiest trying to resolve authentication requests from users logging in after weekend. File servers’ve probably been relatively dormant over weekend as well. Terminal Servers – well, that goes without saying … doesn’t it? By same token, getting a baseline at end of the day isn’t a bad idea either. We just talked about logon / logoff issues on Terminal Servers due to profile issues. Do same “slowness” problems occur on Monday morning and Friday afternoon? You’ll definitely want to get an understanding of server performance during those peak times, as well as at different times during the day – and even during your business cycle (such as year-end processing).

Full Article: Performance team