Maximizing.ASP.dot.NET.Real.World.ObjectOriented.Development [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Maximizing.ASP.dot.NET.Real.World.ObjectOriented.Development [Electronic resources] - نسخه متنی

Jeffrey Putz

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید






Performance Monitor


The Performance monitor built into Windows 2000, XP, and Windows Server 2003 can give you a peek into all kinds of activity on your server. It can be found under the Administrator Tools in your Start menu. Figure 15.1 shows the Performance monitor in action.

Figure 15.1. The Performance monitor.

[View full size image]

In the screenshot, we can see that we're monitoring the total CPU time used, the number of requests being made in a specific IIS application, and the number of batch requests per second being made to SQL Server. Clicking the + button in the toolbar will show you literally hundreds of other things you can measure in real time.

Of course, the first thing you can check when your server appears to be choking is whether its CPU is getting maxed out. This is easy enough to see in the Task Manager, shown in Figure 15.2. You can get to this screen by pressing Ctrl-Alt-Del and choosing it or by right-clicking the task bar and choosing it.

Figure 15.2. The Task Manager Performance and Processes tabs.

[View full size image]

The left side shows the Performance tab, which includes a CPU meter and graph. The right side shows the Processes tab, which lists all of the running processes. You can click the column headings to sort these processes. Here we have the processes sorted by CPU time. You can see that w3wp.exe, the IIS Web serving process, is using a little more CPU than everything else right now. If you watched it in real time, you'd likely see the SQL Server process jump up there from time to time.


/ 146