VMtoday

VMware News, Views, and How-To's from vExpert Josh Townsend

You are here: Home / Scripts & Free Tools / View PAL / VMware View PAL Desktop Sample Report

VMware View PAL Desktop Sample Report

Analysis of “PAL_VMWare_View_PCoIP_and_Guest_Performance.blg”Report Generated at: 9/13/2012 4:19:56 PM PALv2

On This Page

Back to the top

Tool Parameters:
Name Value
Log Time Range: 9/13/2012 4:12:23 PM – 9/13/2012 4:13:20 PM
Log(s): C:Usersjosh.townsendDesktopPAL_VMWare_View_PCoIP_and_Guest_Performance.blg
AnalysisInterval: 2 second(s)
Threshold File: C:Program FilesPALPALPAL_VMwareView_PCoIP.xml
AllCounterStats: False
NumberOfProcessors: 1
vRAMSize: 2
ViewParentSixtyFourBit: True
LinnkedClone: True
SixtyFourBit: True
NumberOfVirtualCPUs: 1
TotalMemory: 2
RAID5Drives: NULL
RAID1Drives: NULL
ThreeGBSwitch: False

Back to the top

Alerts by Chronological Order

Description: This section displays all of the alerts in chronological order.

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:23 PM – 9/13/2012 4:12:26 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:26 PM – 9/13/2012 4:12:29 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 23,050 23,050 23,050 745,200
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,095 1,095 1,095 1,292,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,270,738,944 1,270,738,944 1,270,738,944 50,614,272,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(explorer)Working Set 66,277,376 66,277,376 66,277,376 265,420,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,174,720 102,174,720 102,174,720 15,025,766,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 79,921,152 79,921,152 79,921,152 110,341,324,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 29,233,152 29,233,152 29,233,152 545,587,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,360,576 14,360,576 14,360,576 398,131,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,143,488 78,143,488 78,143,488 884,736,000
More than 50% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 57 57 57 23,400
More than 50% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 57 57 57 23,400
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,526 6,526 6,526 4,176,000
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 23,850 23,850 23,850 1,092,600
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 916 916 916 485,100
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,614,272 1,330,614,272 1,330,614,272 79,194,931,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(csrss#1)Working Set 16,613,376 16,613,376 16,613,376 129,024,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,154,240 102,154,240 102,154,240 7,494,451,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 83,574,784 83,574,784 83,574,784 58,458,931,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,023,680 30,023,680 30,023,680 984,268,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,446,592 14,446,592 14,446,592 276,480,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(SearchIndexer)Working Set 34,668,544 34,668,544 34,668,544 117,964,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,151,680 78,151,680 78,151,680 449,740,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 91 91 91 42,300
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 91 91 91 42,300
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 9 9 9 6,300
Greater than 15ms physical disk READ response times JTOWNSEND-VDPhysicalDisk(0 C:)Avg. Disk sec/Read .019 .019 .019 6
Greater than 15 ms logical disk READ response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk sec/Read .019 .019 .019 6
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 23,664 23,664 23,664 616,800
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,476 1,476 1,476 659,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,950,144 1,330,950,144 1,330,950,144 52,998,144,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,121,472 102,121,472 102,121,472 4,976,640,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 102,309,888 102,309,888 102,309,888 50,213,683,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,068,736 30,068,736 30,068,736 683,212,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,536,704 14,536,704 14,536,704 238,387,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,303,232 78,303,232 78,303,232 390,758,400
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 82 82 82 22,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 82 82 82 22,800
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 8 8 8 3,600
Greater than 25ms physical disk READ response times JTOWNSEND-VDPhysicalDisk(0 C:)Avg. Disk sec/Read .092 .092 .092 48
Greater than 25 ms logical disk READ response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk sec/Read .092 .092 .092 48
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,582 24,582 24,582 875,700
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,476 1,476 1,476 494,550
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,351,532,544 1,351,532,544 1,351,532,544 49,010,688,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 409,190,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,260,736 102,260,736 102,260,736 3,795,148,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 106,827,776 106,827,776 106,827,776 39,693,312,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,068,736 30,068,736 30,068,736 512,409,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,540,800 14,540,800 14,540,800 180,633,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,151,680 78,151,680 78,151,680 224,870,400
This process is using more than 1000 data I/O’s (network or disk) per second JTOWNSEND-VDProcess(iexplore#3)IO Other Operations/sec 1,646 1,646 1,646 388,350
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 24,750
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 24,750
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 27 27 27 4,050
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 27 27 27 4,050
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 3 3 3 450
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,775 7,775 7,775 1,606,050
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 159,147 159,147 159,147 68,512,500
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,582 24,582 24,582 700,560
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,474 1,474 1,474 394,920
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,351,053,312 1,351,053,312 1,351,053,312 39,036,026,880
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 327,352,320
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,244,352 102,244,352 102,244,352 3,030,220,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 116,748,288 116,748,288 116,748,288 35,326,033,920
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,068,736 30,068,736 30,068,736 409,927,680
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,548,992 14,548,992 14,548,992 147,456,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,913,536 78,913,536 78,913,536 454,164,480
This process is using more than 1000 data I/O’s (network or disk) per second JTOWNSEND-VDProcess(pcoip_server_win32)IO Other Operations/sec 1,082 1,082 1,082 352,440
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 19,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 19,800
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 38 38 38 7,200
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 38 38 38 7,200
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 10 10 10 2,880
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 8,337 8,337 8,337 1,487,160
Greater than 25ms physical disk READ response times JTOWNSEND-VDPhysicalDisk(0 C:)Avg. Disk sec/Read .035 .035 .035 8
Greater than 25 ms logical disk READ response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk sec/Read .035 .035 .035 8
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Read 69,778 69,778 69,778 19,848,600
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,580 24,580 24,580 583,200
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,475 1,475 1,475 329,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,347,657,728 1,347,657,728 1,347,657,728 31,511,347,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 272,793,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 94,203,904 94,203,904 94,203,904 113,049,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 117,268,480 117,268,480 117,268,480 29,594,419,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,031,872 30,031,872 30,031,872 330,547,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,561,280 14,561,280 14,561,280 126,566,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,921,728 78,921,728 78,921,728 380,928,000
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 100 100 100 16,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 100 100 100 16,800
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 39 39 39 6,300
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 39 39 39 6,300
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 3 3 3 300
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,036 7,036 7,036 849,000
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,587 24,587 24,587 501,686
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,473 1,473 1,473 281,829
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,343,746,048 1,343,746,048 1,343,746,048 26,003,865,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 233,823,086
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 118,501,376 118,501,376 118,501,376 25,683,675,429
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,031,872 30,031,872 30,031,872 283,326,171
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,561,280 14,561,280 14,561,280 108,485,486
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,635,008 78,635,008 78,635,008 252,781,714
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 14,143
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 14,143
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 44 44 44 6,686
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 44 44 44 6,686
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 10 10 10 2,057
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,550 7,550 7,550 859,886
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 95,279 95,279 95,279 22,726,800
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,588 24,588 24,588 439,200
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,487 1,487 1,487 249,750
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,339,785,216 1,339,785,216 1,339,785,216 21,862,195,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 204,595,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 120,381,440 120,381,440 120,381,440 22,896,230,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,048,256 30,048,256 30,048,256 251,596,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,626,816 14,626,816 14,626,816 109,670,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,364,672 78,364,672 78,364,672 160,358,400
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 100 100 100 12,600
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 100 100 100 12,600
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 40 40 40 4,950
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 40 40 40 4,950
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 13 13 13 2,475
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,179 7,179 7,179 668,925
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,591 24,591 24,591 391,000
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,487 1,487 1,487 222,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,337,192,448 1,337,192,448 1,337,192,448 18,914,508,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 181,862,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 120,696,832 120,696,832 120,696,832 20,415,283,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,048,256 30,048,256 30,048,256 223,641,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,290,944 78,290,944 78,290,944 127,795,200
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 83 83 83 7,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 83 83 83 7,800
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 22 22 22 800
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 22 22 22 800
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 18 18 18 3,200
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 5,749 5,749 5,749 308,600
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 174,033 174,033 174,033 33,427,200
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,594 24,594 24,594 352,440
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,486 1,486 1,486 199,620
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,332,838,400 1,332,838,400 1,332,838,400 16,239,329,280
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 163,676,160
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 122,019,840 122,019,840 122,019,840 18,611,896,320
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,040,064 30,040,064 30,040,064 199,802,880
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,286,848 78,286,848 78,286,848 114,278,400
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 96 96 96 9,360
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 96 96 96 9,360
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 32 32 32 2,520
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 32 32 32 2,520
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 9 9 9 1,260
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,449 6,449 6,449 403,740
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,279 24,279 24,279 268,855
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,486 1,486 1,486 181,473
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,322,061,824 1,322,061,824 1,322,061,824 12,999,586,909
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 148,796,509
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 123,461,632 123,461,632 123,461,632 17,155,835,345
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,044,160 30,044,160 30,044,160 182,309,236
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 9,000
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 9,000
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 39 39 39 3,436
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 39 39 39 3,436
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 15 15 15 2,127
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,704 6,704 6,704 408,764
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,277 24,277 24,277 246,150
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,486 1,486 1,486 166,350
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,320,280,064 1,320,280,064 1,320,280,064 11,649,024,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 136,396,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 124,116,992 124,116,992 124,116,992 15,824,486,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,044,160 30,044,160 30,044,160 167,116,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 91 91 91 7,050
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 91 91 91 7,050
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 29 29 29 1,650
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 29 29 29 1,650
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 12 12 12 1,500
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 8,454 8,454 8,454 637,200
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,277 24,277 24,277 227,215
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,259 1,259 1,259 122,123
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,318,113,280 1,318,113,280 1,318,113,280 10,452,928,985
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 125,904,738
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 139,829,248 139,829,248 139,829,248 16,782,761,354
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,019,584 30,019,584 30,019,584 150,858,831
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 98 98 98 7,477
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 98 98 98 7,477
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 39 39 39 2,908
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 39 39 39 2,908
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 10 10 10 1,108
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,644 6,644 6,644 337,569
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,047 24,047 24,047 181,414
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,500 1,500 1,500 144,386
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,610,176 1,330,610,176 1,330,610,176 11,313,034,971
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 116,911,543
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 150,216,704 150,216,704 150,216,704 16,919,522,743
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,011,392 30,011,392 30,011,392 139,029,943
More than 50% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 69 69 69 3,214
More than 50% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 69 69 69 3,214
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 22 22 22 514
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 22 22 22 514
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 23 23 23 2,700
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,031 7,031 7,031 363,214
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 110,336 110,336 110,336 13,299,300
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,279 24,279 24,279 197,160
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,500 1,500 1,500 134,760
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,337,384,960 1,337,384,960 1,337,384,960 11,371,806,720
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 109,117,440
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 153,907,200 153,907,200 153,907,200 16,234,414,080
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,007,296 30,007,296 30,007,296 129,269,760
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 92 92 92 5,760
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 92 92 92 5,760
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 21 21 21 360
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 21 21 21 360
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 5,751 5,751 5,751 185,400
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 158,446 158,446 158,446 18,185,880
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:11 PM – 9/13/2012 4:13:14 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,289 24,289 24,289 185,962
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,499 1,499 1,499 126,225
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,336,279,040 1,336,279,040 1,336,279,040 10,536,652,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 152,461,312 152,461,312 152,461,312 15,057,100,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 29,925,376 29,925,376 29,925,376 111,974,400
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 15 15 15 1,462
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 211,925 211,925 211,925 23,065,650
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:14 PM – 9/13/2012 4:13:17 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,282 24,282 24,282 174,282
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,499 1,499 1,499 118,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,520,064 1,330,520,064 1,330,520,064 9,307,075,765
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 151,015,424 151,015,424 151,015,424 14,018,294,965
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 116,884 116,884 116,884 11,645,682
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:17 PM – 9/13/2012 4:13:19 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,281 24,281 24,281 164,500
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,499 1,499 1,499 112,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,325,068,288 1,325,068,288 1,325,068,288 8,244,838,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 151,126,016 151,126,016 151,126,016 13,250,560,000
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 396,954 396,954 396,954 39,005,700
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0

Cache

Cache Lazy Write Flushes/sec

Description: Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred by each write operation.

The lazy writer writes 20% of the dirty pages every second, but increases the number of lazy write flushes if it is unable to keep up with the rate of dirty pages.

This analysis checks for more than 100 lazy write flushes/second which might indicate that the lazy writer is falling behind in writing to the disk.

CacheLazy Write Flushes/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition CacheLazy Write Flushes/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 0 5 16 0 5 4 3 3

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Cache Dirty Pages

Description: Total number of dirty pages on the system cache

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition CacheDirty Pages Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 55 541 1,210 35,600 368 468 399 327

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk

LogicalDisk % Free Space

Description: % Free Space is the percentage of total usable space on the selected logical disk drive that was free. Low to no free disk space can cause severe disk performance problems.This analysis checks for less than 10% free disk space (Warning alert) and less than 5% free disk space (Critical alert).

LogicalDisk(*)% Free Space Warning Range: 5 to 10 Critical Range: 0 to 5

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)% Free Space Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/C: 23 23 23 0 0 23 23 23
OK JTOWNSEND-VD/HarddiskVolume1 72 72 72 0 0 72 72 72

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Read Latency Analysis

Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are less than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:

Ruling Out Disk-Bound Problems

https://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

LogicalDisk(*)Avg. Disk sec/Read Warning Range: .015 to .025 Critical Range: .025 to .092

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Avg. Disk sec/Read Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
Greater than 25 ms logical disk READ response times JTOWNSEND-VD/C: .001 .012 .092 -1 .021 .005 .004 .003
OK JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
Greater than 15 ms logical disk READ response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk sec/Read .019 .019 .019 6
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
Greater than 25 ms logical disk READ response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk sec/Read .092 .092 .092 48
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
Greater than 25 ms logical disk READ response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk sec/Read .035 .035 .035 8

Back to the top

LogicalDisk Write Latency Analysis

Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:

Ruling Out Disk-Bound Problems

https://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

LogicalDisk(*)Avg. Disk sec/Write Warning Range: .015 to .025 Critical Range: .025 to .029999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Avg. Disk sec/Write Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/C: .001 .003 .007 0 .001 .002 .002 .002
OK JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk % Idle Time

Description: % Idle Time reports the percentage of time during the sample interval that the disk was idle.

This analysis checks for a % Idle Time of less than 10. Zero (0) indicates that the disk contstanly has at least 1 outstanding I/O in the queue.

Reference:

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)% Idle Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/C: 87 97 100 400 4 97 96 96
OK JTOWNSEND-VD/HarddiskVolume1 100 100 100 0 0 100 100 100

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Disk Transfers/sec

Description: Disk Transfers/sec is the rate of read and write operations on the disk.

LogicalDisk(*)Disk Transfers/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Disk Transfers/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/C: 2 12 31 -1,100 8 10 9 8
No Thresholds JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Read/Write Ratio

Description:
This analysis shows the ratio of reads to writes for each logical disk. For example, a value of 25 means 25 percent of all of the I/O per second is read I/O and 75 percent is write I/O.

LogicalDisk(*)Read Write RatioLogicalDisk(*)Disk Reads/secLogicalDisk(*)Disk Writes/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Read Write Ratio Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/C: 0 6 21 -2,100 7 4 3 2
No Thresholds JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0
Condition LogicalDisk(*)Disk Reads/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/C: 0 1 4 -300 1 1 1 0
No Thresholds JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0
Condition LogicalDisk(*)Disk Writes/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/C: 2 11 28 -800 7 9 8 7
No Thresholds JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Bytes/Read

Description: This analysis shows the size of logical disk reads per second. The size of an I/O request packets (IRP) can have a direct affect on the average response times from the disk. This analysis checks for I/O request sizes of 64 KB or larger. Correlate this analysis with the Avg. Disk Sec/Read and Avg. Disk Sec/Write analyses.

References:

LogicalDisk(*)Avg. Disk Bytes/Read

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Avg. Disk Bytes/Read Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VD/C: 9,216 17,594 69,778 -542,700 14,792 13,361 11,962 10,461
OK JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Read 69,778 69,778 69,778 19,848,600

Back to the top

LogicalDisk Bytes/Write

Description: This analysis shows the size of logical disk writes per second. The size of an I/O request packets (IRP) can have a direct affect on the average response times from the disk. This analysis checks for I/O request sizes of 64 KB or larger. Correlate this analysis with the Avg. Disk Sec/Read and Avg. Disk Sec/Write analyses.

Reference:

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Avg. Disk Bytes/Write Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VD/C: 6,897 85,957 396,954 39,005,700 101,031 60,253 46,074 31,984
OK JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 159,147 159,147 159,147 68,512,500
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 95,279 95,279 95,279 22,726,800
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 174,033 174,033 174,033 33,427,200
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 110,336 110,336 110,336 13,299,300
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 158,446 158,446 158,446 18,185,880
9/13/2012 4:13:11 PM – 9/13/2012 4:13:14 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 211,925 211,925 211,925 23,065,650
9/13/2012 4:13:14 PM – 9/13/2012 4:13:17 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 116,884 116,884 116,884 11,645,682
9/13/2012 4:13:17 PM – 9/13/2012 4:13:19 PM Condition Counter Min Avg Max Hourly Trend
Greater than or equal to 64K I/O Sizes – the larger the I/O size, the longer the response times JTOWNSEND-VDLogicalDisk(C:)Avg. Disk Bytes/Write 396,954 396,954 396,954 39,005,700

Back to the top

LogicalDisk Avg. Disk Queue Length

Description: Avg. Disk Queue Length is the average number of both read and write requests that were queued or “in-flight” for the selected disk during the sample interval.

This counter typically has a threshold of number of spindles + 2. Due to high end disk virtualization, it is difficult to determine the true number of physical spindles behind the logical disk or LUN. Therefore, this threshold will generically throw a Warning alert for an average disk queue length greater than 2.

References:

LogicalDisk(*)Avg. Disk Queue Length Warning Range: 2 to 9.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Avg. Disk Queue Length Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/C: 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Current Disk Queue Length

Description: Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks.

This analysis checks if the number of I/O request packets (IRPs) in the disk queue are at 32 or higher. Many SAN vendors use 32 as a default setting for the Host Bus Adapter (HBA) which interfaces into the fibre channel network to connect to one or more SANs. If the queue depth (simultaneous in-flight I/O) is reached frequently, then the queue depth might need to be increased.

Reference:

LogicalDisk(*)Current Disk Queue Length

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Current Disk Queue Length Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/C: 0 0 1 0 0 0 0 0
OK JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Disk Bytes/sec

Description: Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations. A mirror pair (RAID1) 7200 RPM disk drives can deliver roughly 20 MB per second throughput.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Disk Bytes/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/C: 59,241 686,640 1,759,215 119,904,500 611,869 562,839 432,766 316,534
No Thresholds JTOWNSEND-VD/HarddiskVolume1 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

LogicalDisk Free Megabytes

Description: Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.

LogicalDisk(*)Free Megabytes

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition LogicalDisk(*)Free Megabytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/_Total 7,253 7,253 7,253 0 0 7,253 7,253 7,253
OK JTOWNSEND-VD/C: 7,182 7,182 7,182 0 0 7,182 7,182 7,182
Less than 500 MB of free disk space JTOWNSEND-VD/HarddiskVolume1 71 71 71 0 0 71 71 71

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:23 PM – 9/13/2012 4:12:26 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:26 PM – 9/13/2012 4:12:29 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:11 PM – 9/13/2012 4:13:14 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:14 PM – 9/13/2012 4:13:17 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0
9/13/2012 4:13:17 PM – 9/13/2012 4:13:19 PM Condition Counter Min Avg Max Hourly Trend
Less than 500 MB of free disk space JTOWNSEND-VDLogicalDisk(HarddiskVolume1)Free Megabytes 71 71 71 0

Back to the top

Memory

Memory Available MBytes

Description:
Available MBytes is the amount of physical RAM, in Megabytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists. If this counter is low, then the computer is running low on physical RAM.

This analysis will alert a Warning if this counter’s value is less than 10% of the RAM installed and will alert a critical if this counter’s value is less than 100MB’s. When Windows Server 2003 and newer has less then 100MBs of available RAM, it will go into a low memory condition and alert processes of this condition. If in a low memory condition the operating system will be more aggressive at working set trimming which pages out the physical RAM used by processes to the pagefile on the disk.

References:

MemoryAvailable MBytes Warning Range: 102.4 to 204.8 Critical Range: .001 to 102.4

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryAvailable MBytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 798 814 872 -6,200 18 809 808 806

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Free System Page Table Entries

Description: Free System Page Table Entries is the number of page table entries not currently in used by the system. This analysis determines if the system is running out of free system page table entries (PTEs) by checking if there is less than 20,000 free PTE’s as a Warning and critical if there is less than 8,000 free PTEs. Lack of enough PTEs can result in system wide hangs. Also note that the /3GB switch will lower the amount of free PTEs significantly.

The Performance Monitor MemoryFree System Page Table Entries counter is inaccurate on installations of Windows Server 2003 without Service Pack 1. For more information about this counter, see Microsoft Knowledge Base article 894067. The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003 https://go.microsoft.com/fwlink/?linkid=3052&kbid=894067

Fix for Win2003 SP1 systems with /3GB and low on PTE’s: If the system is low on PTE’s, running Windows 2003, and using /3GB switch, then consider using the /USERVA switch to give back some of the memory to the kernel. Note, this only works for Free System PTE issues.

For more information on the USERVA switch, go to:
How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB

Reference:

Ruling Out Memory-Bound Problems

Microsoft Knowledge Base article 894067 The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003

How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP

https://support.microsoft.com/kb/889654

MemoryFree System Page Table Entries Warning Range: 8,000 to 20,000 Critical Range: 0 to 8,000

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryFree System Page Table Entries Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 33,556,592 33,556,596 33,556,602 -600 3 33,556,596 33,556,595 33,556,595

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Pool Non-Paged Bytes

Description: Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.

This analysis checks to see if the system is becoming close to the maximum Pool Nonpaged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.

If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.

References

How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks

https://support.microsoft.com/kb/177415

Ruling Out Memory-Bound Problems

https://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP

https://support.microsoft.com/kb/889654

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryPool Nonpaged Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 49,692,672 49,844,634 50,110,464 -1,228,800 115,194 49,819,420 49,800,704 49,785,125

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Pool Paged Bytes

Description: This analysis checks to see if the system is becoming close to the maximum Pool paged memory size. Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used.

This analysis checks to see if the system is becoming close to the maximum Pool Paged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.

If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.

Reference:

How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks

https://support.microsoft.com/kb/177415

Ruling Out Memory-Bound Problems

https://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP

https://support.microsoft.com/kb/889654

MemoryPool Paged Bytes Warning Range: 2,242,274,918.4 to 2,989,699,891.199 Critical Range: 2,989,699,891.2 to 3,737,124,864

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryPool Paged Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 151,805,952 151,923,302 152,068,096 8,601,600 64,261 151,907,442 151,898,624 151,891,968

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Pages/sec

Description: This analysis checks to see if the Pages/sec is high while the system is in a low memory condition. If it is sustained at a high amount, then the system is might be running out of memory by trying to page the memory to the disk. Keep in mind that all hard page faults are counted in the pages/sec counter such as hard page faults caused by memory mapped files instead of page file hits.
According to Wikipedia, memory-mapped files are a segment of virtual memory which has been assigned a direct byte-for-byte correlation with some portion of a file or file-like resource. This resource is typically a file that is physically present on-disk, but can also be a device, shared memory object, or other resource that the operating system can reference through a file descriptor.
In other words, applications like Microsoft Word and Microsoft PowerPoint will not load entire documents into RAM. Instead, they memory map the file, so that when you navigate through the document, it loads portions of the document as needed. The act of loading portions of the document from disk to RAM as a memory mapped file causes a hard page fault which is counted in the pages/sec counter. See the article The Case of the Phantom Hard Page Faults. To determine if the hard page faults are actually hitting the page file, use Process Monitor with Advanced Ouput enabled to see how often the page file(s) are hit.

Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. It is the sum of MemoryPages Input/sec and MemoryPages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as MemoryPage Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.

This counter should always be below 1000, therefore this analysis checks for values above 1000. Use this analysis in correlation with Available Memory Analysis and Memory Leak Analysis. If all are throwing alerts at the same time, then this may indicate the system is running out of memory and the suspected processes involved and follow analysis steps mentioned in the Memory Leak analysis.

Reference

MemoryPages/sec Warning Range: 1,000 to 1,999.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryPages/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 1 69 259 24,200 110 46 18 5

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory System Cache Resident Bytes

Description: System Cache Resident Bytes is the size, in bytes, of the pageable operating system code in the file system cache. This value includes only current physical pages and does not include any virtual memory pages not currently resident. It does equal the System Cache value shown in Task Manager. As a result, this value may be smaller than the actual amount of virtual memory in use by the file system cache. This value is a component of MemorySystem Code Resident Bytes which represents all pageable operating system code that is currently in physical memory. This counter displays the last observed value only; it is not an average.

This analysis checks if System Cache Resident Bytes is consuming more than 50 percent of RAM. Under load, a server might use the System Cache in order to cache I/O activity such as disk. Use in correlation with Process IO Data Operations/sec and Process IO Other Operations/sec Analyses.

References

File Cache Performance and Tuning https://technet.microsoft.com/en-us/library/bb742613.aspx

MemorySystem Cache Resident Bytes Warning Range: 1,073,741,824 to 1,932,735,283.2 Critical Range: 1,932,735,283.2 to 2,147,483,648

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemorySystem Cache Resident Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 51,535,872 61,709,926 71,970,816 -1,909,964,800 6,793,013 60,585,529 59,303,680 58,152,082

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Cache Bytes

Description: Cache Bytes is the sum of the MemorySystem Cache Resident Bytes, MemorySystem Driver Resident Bytes, MemorySystem Code Resident Bytes, and MemoryPool Paged Resident Bytes counters. This counter displays the last observed value only; it is not an average.

MemoryCache Bytes Warning Range: 1,610,612,736 to 1,932,735,283.2 Critical Range: 1,932,735,283.2 to 2,147,483,648

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryCache Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 51,535,872 61,709,926 71,970,816 -1,909,964,800 6,793,013 60,585,529 59,303,680 58,152,082

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory % Committed Bytes In Use

Description: % Committed Bytes In Use is the ratio of MemoryCommitted Bytes to the MemoryCommit Limit. Committed memory is the physical memory (RAM plus all of the page files) in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is the sum of physical RAM and the size of all of the paging files. If the paging file is enlarged, the commit limit increases, and the ratio is reduced). This counter displays the current percentage value only; it is not an average.

This analysis checks if the amount of Commited memory is becoming close to the Commit Limit (RAM plus total page file sizes), If so, then identify if you have a memory leak. If no memory leak is identified, then consider adding more physical RAM or increase the size of your page files.

Memory% Committed Bytes In Use Warning Range: 70 to 90 Critical Range: 90 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Memory% Committed Bytes In Use Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 35 37 38 300 1 37 37 37

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Pages Output/sec

Description: Pages Output/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply. This counter shows the number of pages, and can be compared to other counts of pages, without conversion.

MemoryPages Output/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryPages Output/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 63 258 25,600 110 40 12 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Transition Pages RePurposed/sec

Description: Transition Pages RePurposed is the rate at which the number of transition cache pages were reused for a different purpose. These pages would have otherwise remained in the page cache to provide a (fast) soft fault (instead of retrieving it from backing store) in the event the page was accessed in the future. Note these pages can contain private or sharable memory.

MemoryTransition Pages RePurposed/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryTransition Pages RePurposed/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 517 3,890 -119,000 937 277 162 63

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Committed Bytes

Description: Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the memory which has space reserved in RAM and on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.

This analysis checks if the amount of total committed memory (Commit Charge) exceeds the amount of physical RAM installed. If so, the page file needs to be used to help store the committed memory and performance might degrade. To alleviate this, try to identify which process is consuming the most committed memory by looking at process Private Bytes and looking for a potential memory leak (the consumption of memory over a long period of time without releasing it). Adding more RAM to the computer will help alleviate this issue, but if it is a memory leak, then the problem might return.

MemoryCommitted Bytes

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryCommitted Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 1,485,991,936 1,589,391,770 1,621,467,136 13,181,747,200 35,200,210 1,585,946,852 1,581,964,032 1,577,288,265

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Commit Limit

Description: Commit Limit is the amount of virtual memory that can be committed without having to extend the paging file(s). It is measured in bytes. Committed memory is the physical memory which has space reserved on the disk paging files. There can be one paging file on each logical drive). If the paging file(s) are be expanded, this limit increases accordingly. This counter displays the last observed value only; it is not an average.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryCommit Limit Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 4,294,033,408 4,294,033,408 4,294,033,408 0 0 4,294,033,408 4,294,033,408 4,294,033,408

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Pages Input/sec

Description: Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of MemoryPages Input/sec to the value of MemoryPage Reads/sec to determine the average number of pages read into memory during each read operation.

This analysis checks for more than 1000 page inputs per second. If there is a lot of page inputs per second, then it could be normal file I/O reading from the disk as memory mapped files, or it could be reading from the page file. This counter is not an indicator of a lack of memory condition unless there is a lot of memory pressure corresponding to this alert.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryPages Input/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 1 6 25 -1,400 7 4 3 2

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Free & Zero Page List Bytes

Description: Free & Zero Page List Bytes is the amount of physical memory, in bytes, that is assigned to the free and zero page lists. This memory does not contain cached data. It is immediately available for allocation to a process or for system use. For a full explanation of the memory manager, refer to MSDN and/or the System Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.

If the size of the Free and Zero page list is large, then it is a good indicator of too much RAM installed on the computer. A large amount of Free and Zero page list size is normal for computers that have been recently powered on or booted. As the system accesses the hard disk placing pages of memory into the working sets of processes, eventually many of those pages of memory will be discarded or paged out. When that happens, the memory is often placed on the Standby list. A large Standby list is preferable because it uses the extra RAM as a disk cache. Available memory is the sum of the Free, Zero, and Standby page lists, so a high amount of available memory with a low amount of Zero and Free is preferred because the system is using the extra RAM as disk cache.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition MemoryFree & Zero Page List Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 3,230,515 8,499,200 317,030,400 2,927,225 2,658,532 2,082,048 1,602,121

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Inspection System

Network Inspection SystemAverage inspection latency Average inspection latency (sec/bytes)

Description: Average time spent inspecting data (sec/bytes)

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Inspection SystemAverage inspection latency (sec/bytes) Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface

Network Interface % Network Utilization

Description: % Network Utilization doesn’t exist as a normal performance counter, so this analysis uses multiplies Network Interface(*)Bytes Total/sec by 8 (to convert it to bits total/sec), divides it by Network Interface(*)Current Bandwidth, and multiplies the result by 100 to create a percentage. This analysis throws a warning alert when greater than 50 and throws a critical alert when greater than 80.

% Network Utilization Warning Range: 50 to 80 Critical Range: 80 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)% Network Utilization Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 0 1 2 0 1 1 1 1

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Output Queue Length

Description:

Network Interface(*)Output Queue Length Warning Range: 1 to 1.999 Critical Range: 2 to 2.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Output Queue Length Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface % Network Utilization Sent

Description: % Network Utilization Sent doesn’t exist as a normal performance counter, so this analysis uses multiplies Network Interface(*)Bytes Sent/sec by 8 (to convert it to bits total/sec), divides it by Network Interface(*)Current Bandwidth, and multiplies the result by 100 to create a percentage. This analysis throws a warning alert when greater than 50 and throws a critical alert when greater than 80.

% Network Utilization Sent Warning Range: 50 to 80 Critical Range: 80 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)% Network Utilization Sent Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 0 1 1 0 1 1 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface % Network Utilization Received

Description: % Network Utilization Received doesn’t exist as a normal performance counter, so this analysis uses multiplies Network Interface(*)Bytes Received/sec by 8 (to convert it to bits total/sec), divides it by Network Interface(*)Current Bandwidth, and multiplies the result by 100 to create a percentage. This analysis throws a warning alert when greater than 50 and throws a critical alert when greater than 80.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)% Network Utilization Received Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 0 0 1 0 0 0 0 0
OK JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Packets Outbound Errors

Description: Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.

If errors are occuring during this analysis, network connectivity could be affected with a potential for random Outlook RPC dialog boxes. See https://technet.microsoft.com/en-us/library/aa997363.aspx and https://technet.microsoft.com/en-us/library/aa995850.asp for more information

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Packets Outbound Errors Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Bytes Total/sec

Description: Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network InterfaceBytes Total/sec is a sum of Network InterfaceBytes Received/sec and Network InterfaceBytes Sent/sec.

Network Interface(*)Bytes Total/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Bytes Total/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 26,145 993,672 2,184,423 -2,225,800 672,752 861,783 750,954 652,765
No Thresholds JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Current Bandwidth

Description: Current Bandwidth is an estimate of the current bandwidth of the network interface in bits per second (BPS). For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this value is the nominal bandwidth.

Network Interface(*)Current Bandwidth

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Current Bandwidth Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 1,000,000,000 1,000,000,000 1,000,000,000 0 0 1,000,000,000 1,000,000,000 1,000,000,000
No Thresholds JTOWNSEND-VD/isatap.cpsg.local 100,000 100,000 100,000 0 0 100,000 100,000 100,000

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Packets/sec

Description: Packets/sec is the rate at which packets are sent and received on the network interface.

Network Interface(*)Packets/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Packets/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 128 947 1,917 4,800 555 840 748 667
No Thresholds JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Packets Sent/sec

Description: Packets Sent/sec is the rate at which packets are sent on the network interface.

Network Interface(*)Packets Sent/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Packets Sent/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 82 734 1,363 6,100 422 671 605 527
No Thresholds JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network Interface Packets Received/sec

Description: Packets Received/sec is the rate at which packets are received on the network interface.

Network Interface(*)Packets Received/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Network Interface(*)Packets Received/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/Intel[R] PRO_1000 MT Network Connection 20 213 1,015 -1,200 277 142 93 56
No Thresholds JTOWNSEND-VD/isatap.cpsg.local 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Paging File

Paging File % Usage

Description: The amount of the Page File instance in use in percent. See also ProcessPage File Bytes.

This analysis checks if the percentage of usage is greater than 70%.

Reference

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP

https://support.microsoft.com/kb/889654

Paging File(*)% Usage Warning Range: 70 to 90 Critical Range: 90 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Paging File(*)% Usage Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/??C:pagefile.sys 8 8 9 100 0 8 8 8

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PCoIP General

General PCoIP Bytes Received

Description: Total number of bytes that have been received since the PCoIP session started.

PCoIP Session General Statistics(PCoIP Session)Bytes Received

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)Bytes Received Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 6,357,950 6,457,820 6,540,746 17,331,200 56,029 6,449,133 6,439,583 6,429,825

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

General PCoIP Bytes Sent

Description: Total number of bytes that have been transmitted since the PCoIP session started.

PCoIP Session General Statistics(PCoIP Session)Bytes Sent

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)Bytes Sent Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 174,195,796 195,867,159 214,519,992 4,022,015,800 15,350,009 193,800,402 191,271,794 188,426,489

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

General PCoIP Packets Received

Description: Total number of packets that have been received since the PCoIP session started. Note that not all packets are the same size.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)Packets Received Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 58,929 59,860 60,667 164,000 529 59,776 59,686 59,594

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

General PCoIP Packets Sent

Description: Total number of packets that have been transmitted since the PCoIP session started. Note that not all packets are the same size.

PCoIP Session General Statistics(PCoIP Session)Packets Sent

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)Packets Sent Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 221,142 241,757 260,716 3,912,100 14,762 239,676 237,211 234,494

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

General PCoIP RX Packets Lost

Description: Total number of receive packets that have been lost since the PCoIP session started. PCoIP is a UDP based protocol and can tolerate some packet loss. However, because PCoIP is dynamically able to control session, when packet loss is too high, PCoIP will throttle sessions (not just the one with packet loss) to improve the user experience. See https://myvirtualcloud.net/?p=1537 for more info.

PCoIP Session General Statistics(PCoIP Session)RX Packets Lost

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)RX Packets Lost Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

General PCoIP Session Duration Seconds

Description: An incrementing number that represents the total number of seconds the PCoIP session has been open.

PCoIP Session General Statistics(PCoIP Session)Session Duration Seconds

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)Session Duration Seconds Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 12,321 12,350 12,378 5,400 18 12,346 12,344 12,340

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

General PCoIP TX Packets Lost

Description: Total number of transmit packets that have been lost since the PCoIP session started. PCoIP is a UDP based protocol and can tolerate some packet loss. However, because PCoIP is dynamically able to control session, when packet loss is too high, PCoIP will throttle sessions (not just the one with packet loss) to improve the user experience. See https://myvirtualcloud.net/?p=1537 for more info.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session General Statistics(PCoIP Session)TX Packets Lost Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PCoIP Imaging

Imaging Active Minimum Quality

Description: The lowest encoded quality (0 to 100), updated every second. Not to be confused with the GPO setting. Lower minimum image quality will translate to a poorer user experience and a lossy display. Lossy is bad for some settings, such as medial imaging.

PCoIP Session Imaging Statistics(PCoIP Session)Imaging Active Minimum Quality

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging Active Minimum Quality Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 90 90 90 0 0 90 90 90

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Imaging Bytes Received

Description: Total number of imaging bytes that have been received since the PCoIP session started. This value is incremental – it will continue to climb over the term of the PCoIP session. Rapid climbing suggests a user is using a web cam or other video input device.

PCoIP Session Imaging Statistics(PCoIP Session)Imaging Bytes Received

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging Bytes Received Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 3,705,528 3,767,250 3,824,038 10,902,600 35,362 3,761,467 3,755,527 3,749,814

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Imaging Bytes Sent

Description: Total number of imaging bytes that have been sent since the PCoIP session started. This value is incremental – it will continue to climb over the term of the PCoIP session. Rapid climbing suggests a user is streaming video.

PCoIP Session Imaging Statistics(PCoIP Session)Imaging Bytes Sent

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging Bytes Sent Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 164,092,492 184,621,192 202,129,086 3,795,670,200 14,463,388 182,680,309 180,302,486 177,626,808

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Imaging Decoder Capability kbit/sec

Description: The current estimate of the decoder processing capability. This will show how well the client end-point is able to received the data that is being sent to it.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging Decoder Capability kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 16,961 46,865 77,479 -47,200 17,929 43,865 41,064 38,105

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Imaging Encoded Frames/sec

Description: The number of imaging frames which were encoded over a one second sampling period. This can be controlled/throttled by using the ‘PCoIP Image Quality Levels’ Group Policy settings.

PCoIP Session Imaging Statistics(PCoIP Session)Imaging Encoded Frames/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging Encoded Frames/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 7 24 -1,500 6 5 4 4

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Imaging RX BW kbit/sec

Description: Bandwidth for incoming imaging packets averaged over the sampling period (in seconds).

PCoIP Session Imaging Statistics(PCoIP Session)Imaging RX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging RX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 7 16 25 500 4 15 15 14

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Imaging TX BW kbit/sec

Description: Bandwidth for outgoing imaging packets averaged over the sampling period (in seconds).

PCoIP Session Imaging Statistics(PCoIP Session)Imaging TX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Imaging Statistics(PCoIP Session)Imaging TX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 14 5,200 10,202 -14,300 3,538 4,681 4,141 3,541

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PCoIP Network

Network Round Trip Latency ms

Description: Round trip latency (in milliseconds) between server and client. PCoIP is capable of tolerating packet loss and latency as it is a UDP based protocol and able to dynamically manage itself. Howerver, too much loss or latency will result in a poor user experience.

Bandwidth requirements for PCoIP are defined here: https://pubs.vmware.com/view-51/index.jsp?topic=%2Fcom.vmware.view.planning.doc%2FGUID-5DC232B4-778B-4D9C-B995-B8850CF35096.html and here: https://www.vmware.com/files/pdf/view/VMware-View-5-PCoIP-Network-Optimization-Guide.pdf

With the reduced bandwidth consumption in View 5, adding 3D users is satisfactory on a WAN with up to approximately 100ms latency.

Ensure that the round-trip network latency is less than 250 ms as a minimum.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)Round Trip Latency ms Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 6 8 19 -500 3 7 7 6

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network RX BW kbit/sec

Description: Overall bandwidth for incoming PCoIP packets averaged over the sampling period (in seconds).

PCoIP Session Network Statistics(PCoIP Session)RX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)RX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 7 25 43 -1,200 12 23 21 19

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network RX BW Peak kbit/sec

Description: Peak bandwidth for incoming PCoIP packets within a one second sampling period.

PCoIP Session Network Statistics(PCoIP Session)RX BW Peak kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)RX BW Peak kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 21 53 124 4,800 29 46 41 38

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network RX Packet Loss %

Description: Percentage of received packets lost during a sampling period.

PCoIP Session Network Statistics(PCoIP Session)RX Packet Loss %

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)RX Packet Loss % Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network TX BW Active Limit kbit/sec

Description: The current estimate of the available network bandwidth, updated every second.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)TX BW Active Limit kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 50,417 50,417 50,417 0 0 50,417 50,417 50,417

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network TX BW kbit/sec

Description: Overall bandwidth for outgoing PCoIP packets averaged over the sampling period (in seconds).

PCoIP Session Network Statistics(PCoIP Session)TX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)TX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 61 5,513 10,748 -15,900 3,735 4,967 4,399 3,758

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network TX BW Limit kbit/sec

Description: Transmit bandwidth limit for outgoing packets as defined by the minimum of: GPO setting on client and server, local network connection, and Zero Client firmware negotiated value based on encryption limits

PCoIP Session Network Statistics(PCoIP Session)TX BW Limit kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)TX BW Limit kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 90,000 90,000 90,000 0 0 90,000 90,000 90,000

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Network TX Packet Loss %

Description: Percentage of transmitted packets lost during a sampling period.

PCoIP Session Network Statistics(PCoIP Session)TX Packet Loss %

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Network Statistics(PCoIP Session)TX Packet Loss % Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PCoIP Session Audio

Audio Bytes Received

Description: Total number of audio bytes that have been received since the PCoIP session started.

This value is incremental – it will continue to climb over the term of the PCoIP session. Rapid climbing suggests a user is inputing audio – this may be dictation activity (medical or legal settings), WebEx sessions, etc. Consider implementing a PCoIP Group Policy (https://www.vmware.com/files/pdf/view/VMware-View-5-PCoIP-Network-Optimization-Guide.pdf) with the ‘Configure the PCoIP session audio bandwidth limit’ setting enabled. PCoIP Session Audio Bandwidth Limit will configure audio compression to control maximum audio bandwidth.

The audio processing monitors the bandwidth used for audio. The processing selects the audio compression algorithm that provides the best audio possible, given the current bandwidth utilization. If a bandwidth limit is set, the processing reduces quality by changing the compression algorithm selection until the bandwidth limit is reached. If minimum quality audio cannot be provided within the bandwidth limit specified, audio is disabled.

To allow for uncompressed high quality stereo audio, set this value to higher than 1600 kbit/s. A value of 450 kbit/s and higher allows for stereo, high-quality, compressed audio. A value between 50 kbit/s and 450 kbit/s results in audio that ranges between FM radio and phone call quality. A value below 50 kbit/s might result in no audio playback.

This setting applies to View Agent only. You must enable audio on both endpoints before this setting has any effect.

In addition, this setting has no effect on USB audio.

If this setting is disabled or not configured, a default audio bandwidth limit of 500 kilobits per second is configured to constrain the audio compression algorithm selected. If the setting is configured, the value is measured in kilobits per second, with a default audio bandwidth limit of 500 kilobits per second.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Audio Statistics(PCoIP Session)Audio Bytes Received Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Audio Bytes Sent

Description: Total number of audio bytes that have been sent since the PCoIP session started.

This value is incremental – it will continue to climb over the term of the PCoIP session. Rapid climbing suggests a user is streaming audio. Consider implementing a PCoIP Group Policy (https://www.vmware.com/files/pdf/view/VMware-View-5-PCoIP-Network-Optimization-Guide.pdf) with the ‘Configure the PCoIP session audio bandwidth limit’ setting enabled. PCoIP Session Audio Bandwidth Limit will configure audio compression to control maximum audio bandwidth.

The audio processing monitors the bandwidth used for audio. The processing selects the audio compression algorithm that provides the best audio possible, given the current bandwidth utilization. If a bandwidth limit is set, the processing reduces quality by changing the compression algorithm selection until the bandwidth limit is reached. If minimum quality audio cannot be provided within the bandwidth limit specified, audio is disabled.

To allow for uncompressed high quality stereo audio, set this value to higher than 1600 kbit/s. A value of 450 kbit/s and higher allows for stereo, high-quality, compressed audio. A value between 50 kbit/s and 450 kbit/s results in audio that ranges between FM radio and phone call quality. A value below 50 kbit/s might result in no audio playback.

This setting applies to View Agent only. You must enable audio on both endpoints before this setting has any effect.

In addition, this setting has no effect on USB audio.

If this setting is disabled or not configured, a default audio bandwidth limit of 500 kilobits per second is configured to constrain the audio compression algorithm selected. If the setting is configured, the value is measured in kilobits per second, with a default audio bandwidth limit of 500 kilobits per second.

PCoIP Session Audio Statistics(PCoIP Session)Audio Bytes Sent

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Audio Statistics(PCoIP Session)Audio Bytes Sent Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 7,045,786 7,996,544 8,904,104 185,447,800 742,456 7,895,917 7,771,758 7,630,844

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Audio RX BW kbit/sec

Description: Bandwidth for ingoing audio packets averaged over the sampling period (in seconds). Throttle audio bandwidth using Group Policies if needed. Size WAN links to accomodate PCoIP session bandwidth.

PCoIP Session Audio Statistics(PCoIP Session)Audio RX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Audio Statistics(PCoIP Session)Audio RX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Audio TX BW kbit/sec

Description: Bandwidth for outgoing audio packets averaged over the sampling period (in seconds). Throttle audio bandwidth using Group Policies if needed. Size WAN links to accomodate PCoIP session bandwidth.

PCoIP Session Audio Statistics(PCoIP Session)Audio TX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Audio Statistics(PCoIP Session)Audio TX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 254 513 1,000 207 225 191 156

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Audio TX BW Limit kbit/sec

Description: Transmit bandwidth limit for outgoing audio packets as defined by the GPO setting. If you have limited Audio bandwidth in the PCoIP Group Policy, the limit is shown here. See this link for more info: https://pubs.vmware.com/view-51/topic/com.vmware.view.administration.doc/GUID-6C22A209-AFC1-47EF-9DFF-39AFB38D655D.html

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session Audio Statistics(PCoIP Session)Audio TX BW Limit kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 500 500 500 0 0 500 500 500

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PCoIP USB

USB Bytes Received

Description: Total number of USB bytes that have been received since the PCoIP session started.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session USB Statistics(PCoIP Session)USB Bytes Received Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

USB Bytes Sent

Description: Total number of USB bytes that have been sent since the PCoIP session started.

PCoIP Session USB Statistics(PCoIP Session)USB Bytes Sent

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session USB Statistics(PCoIP Session)USB Bytes Sent Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

USB RX BW kbit/sec

Description: Bandwidth for incoming USB packets averaged over the sampling period (in seconds). USB Bandwidth can spike if users are attaching USB Mass Storage Devices, USB Microphones, USB Web Cams, or USB CD/DVD readers/burners. Consider controlling what USB devices users are allowed to connect to a View desktop via Group Polciy (Client or Agent policies -> USB Filtering) https://pubs.vmware.com/view-51/topic/com.vmware.view.administration.doc/GUID-C6E7AF06-1D9F-4096-8753-D6F6C7B58DB1.html#GUID-C6E7AF06-1D9F-4096-8753-D6F6C7B58DB1__TABLE_8F439159BE6344C0BFEED401A49AD9A6

PCoIP Session USB Statistics(PCoIP Session)USB RX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session USB Statistics(PCoIP Session)USB RX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

USB TX BW kbit/sec

Description: Bandwidth for outgoing USB packets averaged over the sampling period (in seconds). USB Bandwidth can spike if users are attaching USB Mass Storage Devices, USB Microphones, USB Web Cams, or USB CD/DVD readers/burners. Consider controlling what USB devices users are allowed to connect to a View desktop via Group Polciy (Client or Agent policies -> USB Filtering) https://pubs.vmware.com/view-51/topic/com.vmware.view.administration.doc/GUID-C6E7AF06-1D9F-4096-8753-D6F6C7B58DB1.html#GUID-C6E7AF06-1D9F-4096-8753-D6F6C7B58DB1__TABLE_8F439159BE6344C0BFEED401A49AD9A6

PCoIP Session USB Statistics(PCoIP Session)USB TX BW kbit/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PCoIP Session USB Statistics(PCoIP Session)USB TX BW kbit/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/PCoIP Session 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PhysicalDisk

PhysicalDisk Read Latency Analysis

Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:

Ruling Out Disk-Bound Problems

https://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

PhysicalDisk(*)Avg. Disk sec/Read Warning Range: .015 to .025 Critical Range: .025 to .092

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PhysicalDisk(*)Avg. Disk sec/Read Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
Greater than 25ms physical disk READ response times JTOWNSEND-VD/0 C: .001 .012 .092 -1 .021 .005 .004 .003

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
Greater than 15ms physical disk READ response times JTOWNSEND-VDPhysicalDisk(0 C:)Avg. Disk sec/Read .019 .019 .019 6
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
Greater than 25ms physical disk READ response times JTOWNSEND-VDPhysicalDisk(0 C:)Avg. Disk sec/Read .092 .092 .092 48
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
Greater than 25ms physical disk READ response times JTOWNSEND-VDPhysicalDisk(0 C:)Avg. Disk sec/Read .035 .035 .035 8

Back to the top

PhysicalDisk Write Latency Analysis

Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.

If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.

If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.

Reference:

Ruling Out Disk-Bound Problems

https://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

PhysicalDisk(*)Avg. Disk sec/Write Warning Range: .015 to .025 Critical Range: .025 to .029999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PhysicalDisk(*)Avg. Disk sec/Write Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/0 C: .001 .003 .007 0 .001 .002 .002 .002

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PhysicalDisk Current Disk Queue Length

Description: Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. For good performance, this difference should average less than two.

If the server is using an HBA (Host Bus Adapter: This is used to connect to a Storage Area Network SAN) and if the Current Disk Queue Length goes up to 32 frequently, then consider increasing the queue depth on the HBA to allow more concurrent I/O to the SAN. Please consult your SAN administrator before making any changes.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PhysicalDisk(*)Current Disk Queue Length Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/0 C: 0 0 1 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PhysicalDisk Avg. Disk Queue Length

Description: Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PhysicalDisk(*)Avg. Disk Queue Length Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/0 C: 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PhysicalDisk Disk Bytes/sec

Description: Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.

PhysicalDisk(*)Disk Bytes/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PhysicalDisk(*)Disk Bytes/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/0 C: 59,241 686,640 1,759,215 119,904,500 611,869 562,839 432,766 316,534

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

PhysicalDisk Calculated IOPS

Description: Disk Reads/sec is the rate of read operations on the disk.

PhysicalDisk(*)Disk Reads/secPhysicalDisk(*)Disk Writes/secPhysicalDisk(*)Calculated IOPS

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition PhysicalDisk(*)Disk Reads/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/0 C: 0 1 4 -300 1 1 1 0
Condition PhysicalDisk(*)Disk Writes/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/0 C: 2 11 28 -800 7 9 8 7
Condition PhysicalDisk(*)Calculated IOPS Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/0 C: 0 12 31 1,500 8 10 8 7

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process

Process Private Bytes

Description: This analysis determines if the system leaking memory over time. A process consuming large portions of memory is okay as long as the process returns the memory back to the system. Look for increasing trends in the chart. An increasing trend over a long period of time could indicate a memory leak. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. This analysis checks for a 10 MB per hour and 5 MB per hour increasing trends. Use this analysis in correlation with the Available Memory analysis.

Use this analysis in correlation with the Available Memory analysis. If you suspect a memory leak condition, then install and use the Debug Diag tool. For more information on the Debug Diag Tool, see the references section.

References:

Debug Diagnostic Tool v1.1 https://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en

Process(*)Private BytesProcess(*)Private BytesProcess(*)Private BytesProcess(*)Private BytesProcess(*)Private BytesProcess(*)Private BytesProcess(*)Private BytesProcess(*)Private Bytes

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)Private Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/_Total 1,008,398,336 1,112,445,542 1,149,136,896 13,786,316,800 37,275,780 1,108,445,412 1,103,671,552 1,098,392,137
OK JTOWNSEND-VD/audiodg 14,536,704 15,277,261 15,458,304 92,160,000 371,569 15,257,145 15,232,000 15,199,671
OK JTOWNSEND-VD/conhost#1 970,752 970,752 970,752 0 0 970,752 970,752 970,752
OK JTOWNSEND-VD/conhost 823,296 823,296 823,296 0 0 823,296 823,296 823,296
OK JTOWNSEND-VD/csrss#1 20,033,536 20,033,536 20,033,536 0 0 20,033,536 20,033,536 20,033,536
OK JTOWNSEND-VD/csrss 2,236,416 2,236,416 2,236,416 0 0 2,236,416 2,236,416 2,236,416
OK JTOWNSEND-VD/dllhost 4,198,400 4,198,400 4,198,400 0 0 4,198,400 4,198,400 4,198,400
OK JTOWNSEND-VD/dwm 2,056,192 2,056,192 2,056,192 0 0 2,056,192 2,056,192 2,056,192
OK JTOWNSEND-VD/explorer 51,183,616 51,324,518 51,384,320 -20,070,400 73,445 51,317,874 51,309,568 51,303,570
OK JTOWNSEND-VD/googletalk 23,351,296 23,351,296 23,351,296 0 0 23,351,296 23,351,296 23,351,296
OK JTOWNSEND-VD/HorizonAgent 4,419,584 4,470,170 4,472,832 0 11,907 4,469,874 4,469,504 4,469,029
OK JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/iexplore#1 81,117,184 81,133,978 81,166,336 -1,228,800 16,325 81,131,065 81,128,192 81,124,791
OK JTOWNSEND-VD/iexplore#2 71,766,016 74,177,741 80,281,600 49,971,200 3,532,992 73,504,313 72,682,240 72,176,494
OK JTOWNSEND-VD/iexplore#3 10,895,360 99,384,482 133,160,960 11,940,249,600 29,934,664 95,495,590 90,856,653 85,697,772
OK JTOWNSEND-VD/iexplore 14,737,408 15,787,622 15,896,576 115,916,800 302,221 15,775,516 15,760,384 15,740,928
OK JTOWNSEND-VD/lsass 6,606,848 6,606,848 6,606,848 0 0 6,606,848 6,606,848 6,606,848
OK JTOWNSEND-VD/lsm 3,223,552 3,228,058 3,231,744 0 4,181 3,227,648 3,227,136 3,226,478
OK JTOWNSEND-VD/mmc 55,959,552 56,588,493 57,024,512 -104,038,400 473,965 56,540,046 56,479,488 56,401,627
OK JTOWNSEND-VD/msdtc 2,801,664 2,801,664 2,801,664 0 0 2,801,664 2,801,664 2,801,664
OK JTOWNSEND-VD/MsMpEng 58,531,840 58,531,840 58,531,840 0 0 58,531,840 58,531,840 58,531,840
OK JTOWNSEND-VD/msseces 6,168,576 6,168,576 6,168,576 0 0 6,168,576 6,168,576 6,168,576
OK JTOWNSEND-VD/OUTLOOK 80,252,928 80,252,928 80,252,928 0 0 80,252,928 80,252,928 80,252,928
OK JTOWNSEND-VD/pcoip_server_win32 93,782,016 93,782,016 93,782,016 0 0 93,782,016 93,782,016 93,782,016
OK JTOWNSEND-VD/rundll32 7,774,208 8,031,027 8,077,312 30,310,400 77,239 8,025,884 8,019,456 8,011,191
OK JTOWNSEND-VD/SearchFilterHost 3,309,568 3,352,166 3,362,816 5,324,800 21,853 3,350,983 3,349,504 3,347,602
OK JTOWNSEND-VD/SearchIndexer 45,797,376 48,081,715 48,635,904 283,033,600 1,119,437 48,020,139 47,943,168 47,844,206
OK JTOWNSEND-VD/SearchProtocolHost#1 2,232,320 2,232,320 2,232,320 0 0 2,232,320 2,232,320 2,232,320
OK JTOWNSEND-VD/SearchProtocolHost 2,232,320 2,296,627 2,387,968 -10,240,000 62,347 2,286,478 2,277,120 2,268,891
OK JTOWNSEND-VD/services 4,628,480 4,679,066 4,681,728 0 11,907 4,678,770 4,678,400 4,677,925
OK JTOWNSEND-VD/smss 417,792 417,792 417,792 0 0 417,792 417,792 417,792
OK JTOWNSEND-VD/spoolsv 9,564,160 9,614,746 9,617,408 0 11,907 9,614,450 9,614,080 9,613,605
OK JTOWNSEND-VD/svchost#1 4,427,776 4,479,181 4,485,120 5,734,400 17,604 4,478,521 4,477,696 4,476,635
OK JTOWNSEND-VD/svchost#10 2,592,768 2,635,366 2,646,016 5,324,800 21,853 2,634,183 2,632,704 2,630,802
OK JTOWNSEND-VD/svchost#2 17,182,720 17,262,797 17,268,736 3,276,800 20,219 17,262,137 17,261,312 17,260,251
OK JTOWNSEND-VD/svchost#3 71,897,088 73,967,002 75,145,216 260,096,000 876,326 73,872,043 73,793,792 73,704,594
OK JTOWNSEND-VD/svchost#4 35,090,432 35,170,304 35,250,176 15,974,400 76,288 35,161,429 35,150,336 35,136,073
OK JTOWNSEND-VD/svchost#5 3,588,096 3,588,096 3,588,096 0 0 3,588,096 3,588,096 3,588,096
OK JTOWNSEND-VD/svchost#6 6,492,160 6,492,160 6,492,160 0 0 6,492,160 6,492,160 6,492,160
OK JTOWNSEND-VD/svchost#7 14,802,944 15,168,102 15,224,832 35,225,600 125,012 15,161,799 15,153,920 15,143,790
OK JTOWNSEND-VD/svchost#8 7,069,696 7,117,619 7,122,944 -5,324,800 16,389 7,117,028 7,116,288 7,115,337
OK JTOWNSEND-VD/svchost#9 1,499,136 1,499,136 1,499,136 0 0 1,499,136 1,499,136 1,499,136
OK JTOWNSEND-VD/svchost 3,682,304 3,682,304 3,682,304 0 0 3,682,304 3,682,304 3,682,304
OK JTOWNSEND-VD/System 143,360 143,360 143,360 0 0 143,360 143,360 143,360
OK JTOWNSEND-VD/SysTrayApp 27,185,152 27,259,699 27,291,648 10,649,600 50,070 27,256,149 27,251,712 27,246,007
OK JTOWNSEND-VD/taskeng 1,859,584 1,859,584 1,859,584 0 0 1,859,584 1,859,584 1,859,584
OK JTOWNSEND-VD/taskhost 8,466,432 8,466,432 8,466,432 0 0 8,466,432 8,466,432 8,466,432
OK JTOWNSEND-VD/TPAutoConnect 3,829,760 3,845,734 3,854,336 2,457,600 12,027 3,844,779 3,843,584 3,842,048
OK JTOWNSEND-VD/TPAutoConnSvc 2,514,944 2,529,690 2,539,520 0 12,353 2,528,597 2,527,232 2,525,477
OK JTOWNSEND-VD/TPVCGateway 2,068,480 2,068,480 2,068,480 0 0 2,068,480 2,068,480 2,068,480
OK JTOWNSEND-VD/vmtoolsd 6,299,648 6,315,622 6,324,224 0 12,027 6,314,667 6,313,472 6,311,936
OK JTOWNSEND-VD/VMUpgradeHelper 1,835,008 1,835,008 1,835,008 0 0 1,835,008 1,835,008 1,835,008
OK JTOWNSEND-VD/vmware-svi-ga 1,486,848 1,486,848 1,486,848 0 0 1,486,848 1,486,848 1,486,848
OK JTOWNSEND-VD/VMwareTray 2,256,896 2,271,642 2,281,472 0 12,353 2,270,549 2,269,184 2,267,429
OK JTOWNSEND-VD/VMwareViewClipboard 10,457,088 10,517,299 10,571,776 -5,734,400 57,268 10,511,246 10,503,680 10,493,952
OK JTOWNSEND-VD/VMWVvphelper 2,998,272 2,998,272 2,998,272 0 0 2,998,272 2,998,272 2,998,272
OK JTOWNSEND-VD/wininit 1,335,296 1,335,296 1,335,296 0 0 1,335,296 1,335,296 1,335,296
OK JTOWNSEND-VD/winlogon 2,523,136 2,523,136 2,523,136 0 0 2,523,136 2,523,136 2,523,136
OK JTOWNSEND-VD/WmiApSrv 1,892,352 1,892,352 1,892,352 0 0 1,892,352 1,892,352 1,892,352
OK JTOWNSEND-VD/WmiPrvSE#1 2,244,608 2,244,608 2,244,608 0 0 2,244,608 2,244,608 2,244,608
OK JTOWNSEND-VD/WmiPrvSE 6,627,328 6,627,328 6,627,328 0 0 6,627,328 6,627,328 6,627,328
OK JTOWNSEND-VD/wsnm 6,459,392 6,474,138 6,483,968 -2,457,600 12,353 6,473,045 6,471,680 6,469,925
OK JTOWNSEND-VD/wsnm_jms 68,325,376 68,372,070 68,403,200 -7,782,400 39,116 68,368,612 68,364,288 68,358,729
OK JTOWNSEND-VD/wssm 3,100,672 3,100,672 3,100,672 0 0 3,100,672 3,100,672 3,100,672
OK JTOWNSEND-VD/wuauclt 1,744,896 1,744,896 1,744,896 0 0 1,744,896 1,744,896 1,744,896

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process Handle Count

Description: This analysis checks overall system to determine how many handles the system has open to determine if there is a handle leak. Handle leaks can be attributed to memory leak. If this analysis throws alerts, then you need to manually open the performance monitor log and look at the instances Process(*)Handle Count to determine which process is leaking handles. Note: The normal System Overview analysis checks all of the processes.

Process(*)Handle CountProcess(*)Handle CountProcess(*)Handle CountProcess(*)Handle CountProcess(*)Handle Count

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)Handle Count Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VD/_Total 22,636 24,179 24,594 164,500 528 24,133 24,077 24,004
OK JTOWNSEND-VD/audiodg 120 145 151 3,000 12 144 143 142
OK JTOWNSEND-VD/conhost#1 33 33 33 0 0 33 33 33
OK JTOWNSEND-VD/conhost 33 33 33 0 0 33 33 33
OK JTOWNSEND-VD/csrss#1 620 649 658 2,900 9 648 646 645
OK JTOWNSEND-VD/csrss 608 613 619 200 4 613 612 611
OK JTOWNSEND-VD/dllhost 190 190 190 0 0 190 190 190
OK JTOWNSEND-VD/dwm 102 103 103 100 0 103 103 103
OK JTOWNSEND-VD/explorer 1,012 1,014 1,015 200 1 1,014 1,014 1,014
OK JTOWNSEND-VD/googletalk 463 463 463 0 0 463 463 463
OK JTOWNSEND-VD/HorizonAgent 234 236 236 0 1 235 235 235
OK JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/iexplore#1 738 741 742 400 2 741 741 741
OK JTOWNSEND-VD/iexplore#2 883 891 903 -1,100 3 890 890 890
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VD/iexplore#3 377 1,366 1,500 112,200 287 1,350 1,330 1,305
OK JTOWNSEND-VD/iexplore 551 591 603 4,300 11 590 589 588
OK JTOWNSEND-VD/lsass 957 971 977 800 6 971 970 969
OK JTOWNSEND-VD/lsm 213 213 214 -100 0 213 213 213
OK JTOWNSEND-VD/mmc 665 672 680 -700 7 671 670 669
OK JTOWNSEND-VD/msdtc 142 142 142 0 0 142 142 142
OK JTOWNSEND-VD/MsMpEng 268 268 268 0 0 268 268 268
OK JTOWNSEND-VD/msseces 255 255 255 0 0 255 255 255
OK JTOWNSEND-VD/OUTLOOK 2,236 2,238 2,244 0 2 2,238 2,238 2,238
OK JTOWNSEND-VD/pcoip_server_win32 945 945 945 0 0 945 945 945
OK JTOWNSEND-VD/rundll32 263 263 263 0 0 263 263 263
OK JTOWNSEND-VD/SearchFilterHost 100 102 103 300 1 102 102 102
OK JTOWNSEND-VD/SearchIndexer 922 930 942 200 9 929 927 925
OK JTOWNSEND-VD/SearchProtocolHost#1 272 272 272 0 0 272 272 272
OK JTOWNSEND-VD/SearchProtocolHost 272 274 276 -400 2 274 274 273
OK JTOWNSEND-VD/services 224 226 226 100 1 226 226 226
OK JTOWNSEND-VD/smss 29 29 29 0 0 29 29 29
OK JTOWNSEND-VD/spoolsv 356 358 358 0 1 358 358 358
OK JTOWNSEND-VD/svchost#1 350 355 357 500 2 355 355 354
OK JTOWNSEND-VD/svchost#10 146 148 149 300 1 148 148 148
OK JTOWNSEND-VD/svchost#2 526 527 532 -500 1 527 527 527
OK JTOWNSEND-VD/svchost#3 452 455 456 300 2 455 454 454
OK JTOWNSEND-VD/svchost#4 1,348 1,359 1,368 1,700 7 1,358 1,357 1,355
OK JTOWNSEND-VD/svchost#5 178 178 178 0 0 178 178 178
OK JTOWNSEND-VD/svchost#6 600 600 600 0 0 600 600 600
OK JTOWNSEND-VD/svchost#7 588 603 606 1,600 5 603 603 602
OK JTOWNSEND-VD/svchost#8 206 209 211 -500 1 209 209 208
OK JTOWNSEND-VD/svchost#9 94 94 94 0 0 94 94 94
OK JTOWNSEND-VD/svchost 370 372 374 100 2 372 372 372
OK JTOWNSEND-VD/System 583 586 588 300 1 586 586 586
OK JTOWNSEND-VD/SysTrayApp 564 570 576 1,200 4 569 568 567
OK JTOWNSEND-VD/taskeng 86 87 88 200 1 87 87 87
OK JTOWNSEND-VD/taskhost 196 198 199 -100 1 198 198 198
OK JTOWNSEND-VD/TPAutoConnect 176 176 178 200 1 176 176 176
OK JTOWNSEND-VD/TPAutoConnSvc 132 132 134 -200 1 132 132 132
OK JTOWNSEND-VD/TPVCGateway 100 100 100 0 0 100 100 100
OK JTOWNSEND-VD/vmtoolsd 234 234 236 0 1 234 234 234
OK JTOWNSEND-VD/VMUpgradeHelper 88 88 88 0 0 88 88 88
OK JTOWNSEND-VD/vmware-svi-ga 92 92 92 0 0 92 92 92
OK JTOWNSEND-VD/VMwareTray 77 78 79 -200 1 78 78 77
OK JTOWNSEND-VD/VMwareViewClipboard 122 123 124 -100 1 123 123 123
OK JTOWNSEND-VD/VMWVvphelper 113 113 113 0 0 113 113 113
OK JTOWNSEND-VD/wininit 73 73 73 0 0 73 73 73
OK JTOWNSEND-VD/winlogon 114 114 114 0 0 114 114 114
OK JTOWNSEND-VD/WmiApSrv 115 115 115 0 0 115 115 115
OK JTOWNSEND-VD/WmiPrvSE#1 115 115 115 0 0 115 115 115
OK JTOWNSEND-VD/WmiPrvSE 264 264 264 0 0 264 264 264
OK JTOWNSEND-VD/wsnm 336 337 338 -200 1 337 337 337
OK JTOWNSEND-VD/wsnm_jms 458 459 460 -200 1 459 459 459
OK JTOWNSEND-VD/wssm 152 152 152 0 0 152 152 152
OK JTOWNSEND-VD/wuauclt 90 90 90 0 0 90 90 90

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:26 PM – 9/13/2012 4:12:29 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 23,050 23,050 23,050 745,200
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,095 1,095 1,095 1,292,400
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 23,850 23,850 23,850 1,092,600
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 916 916 916 485,100
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 23,664 23,664 23,664 616,800
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,476 1,476 1,476 659,400
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,582 24,582 24,582 875,700
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,476 1,476 1,476 494,550
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,582 24,582 24,582 700,560
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,474 1,474 1,474 394,920
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,580 24,580 24,580 583,200
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,475 1,475 1,475 329,400
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,587 24,587 24,587 501,686
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,473 1,473 1,473 281,829
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,588 24,588 24,588 439,200
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,487 1,487 1,487 249,750
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,591 24,591 24,591 391,000
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,487 1,487 1,487 222,000
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,594 24,594 24,594 352,440
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,486 1,486 1,486 199,620
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,279 24,279 24,279 268,855
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,486 1,486 1,486 181,473
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,277 24,277 24,277 246,150
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,486 1,486 1,486 166,350
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,277 24,277 24,277 227,215
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,259 1,259 1,259 122,123
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,047 24,047 24,047 181,414
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,500 1,500 1,500 144,386
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,279 24,279 24,279 197,160
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,500 1,500 1,500 134,760
9/13/2012 4:13:11 PM – 9/13/2012 4:13:14 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,289 24,289 24,289 185,962
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,499 1,499 1,499 126,225
9/13/2012 4:13:14 PM – 9/13/2012 4:13:17 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,282 24,282 24,282 174,282
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,499 1,499 1,499 118,800
9/13/2012 4:13:17 PM – 9/13/2012 4:13:19 PM Condition Counter Min Avg Max Hourly Trend
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(_Total)Handle Count 24,281 24,281 24,281 164,500
Possible Handle Leak: More than 500 handles between overall Min and overall Max and an increasing trend of more than 500 handles per hour JTOWNSEND-VDProcess(iexplore#3)Handle Count 1,499 1,499 1,499 112,200

Back to the top

Process Thread Count

Description: The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.

This analysis checks all of the processes to determine if a process has more than 500 threads and if it is on an increasing trend of 50 threads per hour. A process with a large number of threads and/or an aggressive upward trend could indicate a thread leak which typically results in either a memory leak or high context switching. High context switching will result in high privileged mode CPU.

Process(*)Thread CountProcess(*)Thread CountProcess(*)Thread CountProcess(*)Thread CountProcess(*)Thread CountProcess(*)Thread CountProcess(*)Thread CountProcess(*)Thread Count

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)Thread Count Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/_Total 816 865 880 5,100 15 864 862 860
OK JTOWNSEND-VD/audiodg 5 8 8 300 1 7 7 7
OK JTOWNSEND-VD/conhost#1 1 1 1 0 0 1 1 1
OK JTOWNSEND-VD/conhost 2 2 2 0 0 2 2 2
OK JTOWNSEND-VD/csrss#1 15 15 15 0 0 15 15 15
OK JTOWNSEND-VD/csrss 9 9 9 0 0 9 9 9
OK JTOWNSEND-VD/dllhost 13 13 13 0 0 13 13 13
OK JTOWNSEND-VD/dwm 4 4 4 0 0 4 4 4
OK JTOWNSEND-VD/explorer 33 33 33 0 0 33 33 33
OK JTOWNSEND-VD/googletalk 18 18 18 0 0 18 18 18
OK JTOWNSEND-VD/HorizonAgent 12 13 13 0 0 13 13 13
OK JTOWNSEND-VD/Idle 1 1 1 0 0 1 1 1
OK JTOWNSEND-VD/iexplore#1 21 21 21 0 0 21 21 21
OK JTOWNSEND-VD/iexplore#2 26 27 27 0 1 27 26 26
OK JTOWNSEND-VD/iexplore#3 16 35 37 2,100 5 35 35 34
OK JTOWNSEND-VD/iexplore 16 20 21 500 1 20 20 20
OK JTOWNSEND-VD/lsass 9 9 9 0 0 9 9 9
OK JTOWNSEND-VD/lsm 11 11 11 0 0 11 11 11
OK JTOWNSEND-VD/mmc 15 19 22 -700 3 18 18 17
OK JTOWNSEND-VD/msdtc 12 12 12 0 0 12 12 12
OK JTOWNSEND-VD/MsMpEng 9 9 9 0 0 9 9 9
OK JTOWNSEND-VD/msseces 5 5 5 0 0 5 5 5
OK JTOWNSEND-VD/OUTLOOK 30 30 30 0 0 30 30 30
OK JTOWNSEND-VD/pcoip_server_win32 37 37 37 0 0 37 37 37
OK JTOWNSEND-VD/rundll32 8 9 9 100 0 9 9 9
OK JTOWNSEND-VD/SearchFilterHost 4 5 5 100 0 5 5 5
OK JTOWNSEND-VD/SearchIndexer 13 14 14 0 0 14 14 14
OK JTOWNSEND-VD/SearchProtocolHost#1 7 7 7 0 0 7 7 7
OK JTOWNSEND-VD/SearchProtocolHost 6 7 7 100 1 7 6 6
OK JTOWNSEND-VD/services 6 7 7 0 0 7 7 7
OK JTOWNSEND-VD/smss 3 3 3 0 0 3 3 3
OK JTOWNSEND-VD/spoolsv 13 14 14 0 0 14 14 14
OK JTOWNSEND-VD/svchost#1 8 9 9 100 0 9 9 9
OK JTOWNSEND-VD/svchost#10 10 11 11 100 0 11 11 11
OK JTOWNSEND-VD/svchost#2 19 20 20 0 0 20 20 20
OK JTOWNSEND-VD/svchost#3 18 18 18 0 0 18 18 18
OK JTOWNSEND-VD/svchost#4 35 36 38 300 1 36 36 36
OK JTOWNSEND-VD/svchost#5 6 6 6 0 0 6 6 6
OK JTOWNSEND-VD/svchost#6 13 13 13 0 0 13 13 13
OK JTOWNSEND-VD/svchost#7 23 27 27 400 1 27 26 26
OK JTOWNSEND-VD/svchost#8 12 13 13 -100 0 13 13 13
OK JTOWNSEND-VD/svchost#9 5 5 5 0 0 5 5 5
OK JTOWNSEND-VD/svchost 10 10 10 0 0 10 10 10
OK JTOWNSEND-VD/System 98 100 103 400 2 100 100 99
OK JTOWNSEND-VD/SysTrayApp 9 10 11 200 1 10 10 10
OK JTOWNSEND-VD/taskeng 7 7 7 0 0 7 7 7
OK JTOWNSEND-VD/taskhost 9 9 9 0 0 9 9 9
OK JTOWNSEND-VD/TPAutoConnect 11 12 12 100 0 12 12 12
OK JTOWNSEND-VD/TPAutoConnSvc 8 9 9 0 1 9 8 8
OK JTOWNSEND-VD/TPVCGateway 5 5 5 0 0 5 5 5
OK JTOWNSEND-VD/vmtoolsd 6 7 7 0 0 7 7 6
OK JTOWNSEND-VD/VMUpgradeHelper 4 4 4 0 0 4 4 4
OK JTOWNSEND-VD/vmware-svi-ga 4 4 4 0 0 4 4 4
OK JTOWNSEND-VD/VMwareTray 4 5 5 0 1 5 4 4
OK JTOWNSEND-VD/VMwareViewClipboard 7 8 9 -100 1 8 8 8
OK JTOWNSEND-VD/VMWVvphelper 5 5 5 0 0 5 5 5
OK JTOWNSEND-VD/wininit 3 3 3 0 0 3 3 3
OK JTOWNSEND-VD/winlogon 3 3 3 0 0 3 3 3
OK JTOWNSEND-VD/WmiApSrv 4 4 4 0 0 4 4 4
OK JTOWNSEND-VD/WmiPrvSE#1 5 5 5 0 0 5 5 5
OK JTOWNSEND-VD/WmiPrvSE 6 6 6 0 0 6 6 6
OK JTOWNSEND-VD/wsnm 27 28 28 -100 1 28 28 27
OK JTOWNSEND-VD/wsnm_jms 39 41 42 -300 2 41 40 40
OK JTOWNSEND-VD/wssm 11 11 11 0 0 11 11 11
OK JTOWNSEND-VD/wuauclt 3 3 3 0 0 3 3 3

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process Working Set

Description: Working Set is the current size, in bytes, of the Working Set of a process. The Working Set is the set of memory pages touched recently by the threads in the process. It is the amount of RAM consumed by each process. If available physical memory (RAM) in the computer is above a threshold, pages are left in the Working Set of a process longer. When available memory falls below a threshold, pages are trimmed from Working Sets more frequently than when not in a low available memory condition. If the trimmed page are still in RAM, but not in the processes working set (due to being trimmed), then some of them may be soft-faulted (RAM to RAM) back into the Working Set.

This analysis checks for an increasing trend of 100 MB or more per hour in all of the processes combined. This could be an aggressive working set (RAM usage) leak, but keep in mind that this is only tracking the amount of RAM used by all of the processes and does not include committed memory that has trimmed from the working set. This is generally why Private Bytes is a better counter to use for general memory leaks. With that said, Working Set is a helpful counter to have when analyzing low physical memory conditions that might be induced by page locking which can preven the virtual memory manager from trimming. Use this analysis in correlation with Available Memory Analysis.

Reference:

Process(*)Working SetProcess(*)Working SetProcess(*)Working SetProcess(*)Working SetProcess(*)Working SetProcess(*)Working SetProcess(*)Working SetProcess(*)Working Set

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)Working Set Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VD/_Total 1,242,619,904 1,326,071,808 1,351,532,544 8,244,838,400 26,035,031 1,323,269,461 1,320,465,408 1,317,876,882
OK JTOWNSEND-VD/audiodg 15,544,320 16,274,227 16,453,632 90,931,200 368,174 16,254,293 16,229,376 16,197,339
OK JTOWNSEND-VD/conhost#1 3,014,656 3,148,390 3,276,800 -26,214,400 87,812 3,134,123 3,119,104 3,102,720
OK JTOWNSEND-VD/conhost 2,162,688 2,176,410 2,183,168 -1,638,400 5,984 2,175,659 2,174,720 2,173,806
OK JTOWNSEND-VD/csrss#1 16,379,904 16,577,946 16,678,912 -1,228,800 80,838 16,567,182 16,554,240 16,545,792
OK JTOWNSEND-VD/csrss 3,555,328 3,861,504 4,120,576 -54,067,200 215,510 3,832,718 3,796,992 3,753,399
OK JTOWNSEND-VD/dllhost 7,307,264 7,432,806 7,573,504 -26,624,000 84,030 7,417,173 7,403,264 7,390,647
OK JTOWNSEND-VD/dwm 7,131,136 7,310,541 7,442,432 -27,033,600 104,103 7,295,886 7,279,616 7,261,915
OK JTOWNSEND-VD/explorer 61,976,576 63,755,264 66,277,376 -406,732,800 1,387,769 63,483,221 63,182,336 62,964,882
OK JTOWNSEND-VD/googletalk 33,251,328 35,774,259 37,314,560 -396,083,200 1,323,216 35,603,115 35,416,832 35,217,701
OK JTOWNSEND-VD/HorizonAgent 10,055,680 10,220,749 10,395,648 -32,768,000 124,039 10,201,316 10,181,888 10,161,883
OK JTOWNSEND-VD/Idle 24,576 24,576 24,576 0 0 24,576 24,576 24,576
OK JTOWNSEND-VD/iexplore#1 107,839,488 108,409,037 108,920,832 -105,267,200 325,901 108,352,398 108,291,840 108,247,918
OK JTOWNSEND-VD/iexplore#2 93,827,072 96,179,200 102,260,736 41,779,200 3,563,038 95,504,384 94,671,872 94,168,795
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VD/iexplore#3 18,620,416 118,579,200 153,907,200 13,250,560,000 32,620,219 114,508,017 109,632,990 104,188,377
OK JTOWNSEND-VD/iexplore 28,930,048 29,906,739 30,068,736 88,883,200 297,347 29,888,740 29,867,520 29,841,993
OK JTOWNSEND-VD/lsass 12,976,128 13,522,125 14,159,872 -113,049,600 445,658 13,451,264 13,369,600 13,285,669
OK JTOWNSEND-VD/lsm 5,734,400 5,835,162 5,967,872 -23,347,200 96,100 5,821,554 5,805,824 5,787,355
OK JTOWNSEND-VD/mmc 71,024,640 77,016,064 81,039,360 -960,512,000 3,551,517 76,570,624 76,060,416 75,486,647
OK JTOWNSEND-VD/msdtc 4,501,504 4,555,366 4,579,328 -6,963,200 29,093 4,552,704 4,549,376 4,545,097
OK JTOWNSEND-VD/MsMpEng 7,073,792 7,520,051 7,835,648 -70,860,800 278,710 7,484,985 7,442,176 7,390,354
OK JTOWNSEND-VD/msseces 12,738,560 14,174,822 15,228,928 -239,206,400 765,264 14,057,700 13,935,872 13,816,101
OK JTOWNSEND-VD/OUTLOOK 122,798,080 130,805,146 141,029,376 -1,772,339,200 6,579,146 129,669,120 128,335,872 127,073,134
OK JTOWNSEND-VD/pcoip_server_win32 64,626,688 65,510,195 65,970,176 -95,436,800 316,916 65,459,314 65,410,048 65,366,309
OK JTOWNSEND-VD/rundll32 14,139,392 14,562,918 14,630,912 49,152,000 123,464 14,555,364 14,545,920 14,533,778
OK JTOWNSEND-VD/SearchFilterHost 7,335,936 7,350,886 7,356,416 2,048,000 7,893 7,350,272 7,349,504 7,348,517
OK JTOWNSEND-VD/SearchIndexer 30,355,456 32,930,202 34,668,544 -387,481,600 1,473,976 32,744,107 32,519,936 32,253,367
OK JTOWNSEND-VD/SearchProtocolHost#1 6,676,480 6,676,480 6,676,480 0 0 6,676,480 6,676,480 6,676,480
OK JTOWNSEND-VD/SearchProtocolHost 6,676,480 7,514,317 8,196,096 -147,456,000 759,878 7,438,564 7,344,896 7,225,637
OK JTOWNSEND-VD/services 7,106,560 7,152,026 7,163,904 -2,867,200 14,672 7,150,706 7,149,056 7,146,935
OK JTOWNSEND-VD/smss 921,600 941,466 954,368 -2,867,200 11,907 940,032 938,240 935,936
OK JTOWNSEND-VD/spoolsv 11,804,672 12,865,946 13,623,296 -181,452,800 629,120 12,781,796 12,692,480 12,593,152
OK JTOWNSEND-VD/svchost#1 7,815,168 7,894,221 7,966,720 -10,649,600 51,590 7,886,620 7,879,168 7,871,342
OK JTOWNSEND-VD/svchost#10 10,379,264 10,405,888 10,448,896 -4,915,200 22,611 10,401,109 10,396,928 10,392,430
OK JTOWNSEND-VD/svchost#2 16,109,568 16,582,656 16,957,440 -82,329,600 290,767 16,541,241 16,492,288 16,436,370
OK JTOWNSEND-VD/svchost#3 77,651,968 78,345,011 78,958,592 45,056,000 310,733 78,278,884 78,216,960 78,192,640
OK JTOWNSEND-VD/svchost#4 36,306,944 39,492,813 42,754,048 -611,123,200 2,159,987 39,131,364 38,731,264 38,347,045
OK JTOWNSEND-VD/svchost#5 8,372,224 8,458,854 8,540,160 -16,384,000 54,974 8,449,820 8,440,576 8,431,909
OK JTOWNSEND-VD/svchost#6 9,023,488 9,325,978 9,900,032 -85,606,400 331,392 9,262,194 9,191,168 9,128,521
OK JTOWNSEND-VD/svchost#7 14,950,400 15,109,734 15,466,496 -47,104,000 176,706 15,070,777 15,034,880 15,006,281
OK JTOWNSEND-VD/svchost#8 6,516,736 6,641,050 6,803,456 -28,262,400 107,817 6,623,004 6,601,728 6,580,809
OK JTOWNSEND-VD/svchost#9 4,001,792 4,044,800 4,067,328 -6,553,600 24,086 4,042,297 4,039,424 4,036,023
OK JTOWNSEND-VD/svchost 7,622,656 7,745,536 7,921,664 -28,262,400 116,400 7,726,421 7,703,040 7,679,707
OK JTOWNSEND-VD/System 1,159,168 1,165,517 1,171,456 -819,200 3,869 1,165,084 1,164,800 1,164,434
OK JTOWNSEND-VD/SysTrayApp 31,518,720 33,551,565 36,499,456 -463,257,600 1,493,122 33,224,021 32,908,032 32,715,922
OK JTOWNSEND-VD/taskeng 4,907,008 4,909,056 4,911,104 409,600 2,101 4,908,828 4,908,544 4,908,178
OK JTOWNSEND-VD/taskhost 10,153,984 10,295,706 10,440,704 -27,443,200 102,589 10,279,595 10,261,248 10,245,266
OK JTOWNSEND-VD/TPAutoConnect 10,682,368 11,069,030 11,378,688 -65,126,400 238,078 11,034,624 10,995,712 10,955,630
OK JTOWNSEND-VD/TPAutoConnSvc 6,422,528 6,443,418 6,488,064 -6,553,600 18,742 6,438,457 6,435,584 6,433,938
OK JTOWNSEND-VD/TPVCGateway 4,734,976 4,860,928 5,013,504 -27,852,800 106,030 4,843,975 4,824,064 4,802,560
OK JTOWNSEND-VD/vmtoolsd 8,560,640 8,643,174 8,724,480 -16,384,000 48,851 8,635,051 8,626,944 8,620,617
OK JTOWNSEND-VD/VMUpgradeHelper 4,870,144 4,932,403 5,009,408 -13,107,200 49,109 4,923,847 4,914,432 4,906,423
OK JTOWNSEND-VD/vmware-svi-ga 3,969,024 4,157,235 4,227,072 -25,395,200 90,518 4,149,476 4,139,776 4,129,061
OK JTOWNSEND-VD/VMwareTray 5,656,576 6,027,469 6,389,760 -70,451,200 245,456 5,987,214 5,945,088 5,899,995
OK JTOWNSEND-VD/VMwareViewClipboard 6,062,080 6,332,416 6,520,832 -38,912,000 148,238 6,312,846 6,291,712 6,268,343
OK JTOWNSEND-VD/VMWVvphelper 6,107,136 6,413,312 6,688,768 -57,344,000 200,239 6,382,706 6,350,336 6,313,984
OK JTOWNSEND-VD/wininit 3,551,232 3,577,037 3,592,192 -4,096,000 14,564 3,575,353 3,573,504 3,571,419
OK JTOWNSEND-VD/winlogon 6,316,032 6,457,139 6,692,864 -35,635,200 109,959 6,430,948 6,413,056 6,403,218
OK JTOWNSEND-VD/WmiApSrv 6,750,208 6,750,208 6,750,208 0 0 6,750,208 6,750,208 6,750,208
OK JTOWNSEND-VD/WmiPrvSE#1 4,780,032 4,796,416 4,812,800 -3,276,800 12,466 4,794,596 4,792,576 4,790,272
OK JTOWNSEND-VD/WmiPrvSE 8,486,912 8,795,341 9,445,376 -94,617,600 329,060 8,723,115 8,652,544 8,600,137
OK JTOWNSEND-VD/wsnm 11,857,920 12,242,125 12,431,360 -49,971,200 189,088 12,221,099 12,195,072 12,164,827
OK JTOWNSEND-VD/wsnm_jms 37,822,464 37,854,413 37,875,712 -5,324,800 26,764 37,852,046 37,849,088 37,845,285
OK JTOWNSEND-VD/wssm 7,786,496 8,315,904 8,925,184 -111,411,200 394,485 8,248,206 8,172,032 8,097,207
OK JTOWNSEND-VD/wuauclt 5,820,416 6,140,109 6,414,336 -55,296,000 183,523 6,109,639 6,073,856 6,043,063

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:26 PM – 9/13/2012 4:12:29 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,270,738,944 1,270,738,944 1,270,738,944 50,614,272,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(explorer)Working Set 66,277,376 66,277,376 66,277,376 265,420,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,174,720 102,174,720 102,174,720 15,025,766,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 79,921,152 79,921,152 79,921,152 110,341,324,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 29,233,152 29,233,152 29,233,152 545,587,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,360,576 14,360,576 14,360,576 398,131,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,143,488 78,143,488 78,143,488 884,736,000
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,614,272 1,330,614,272 1,330,614,272 79,194,931,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(csrss#1)Working Set 16,613,376 16,613,376 16,613,376 129,024,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,154,240 102,154,240 102,154,240 7,494,451,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 83,574,784 83,574,784 83,574,784 58,458,931,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,023,680 30,023,680 30,023,680 984,268,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,446,592 14,446,592 14,446,592 276,480,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(SearchIndexer)Working Set 34,668,544 34,668,544 34,668,544 117,964,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,151,680 78,151,680 78,151,680 449,740,800
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,950,144 1,330,950,144 1,330,950,144 52,998,144,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,121,472 102,121,472 102,121,472 4,976,640,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 102,309,888 102,309,888 102,309,888 50,213,683,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,068,736 30,068,736 30,068,736 683,212,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,536,704 14,536,704 14,536,704 238,387,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,303,232 78,303,232 78,303,232 390,758,400
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,351,532,544 1,351,532,544 1,351,532,544 49,010,688,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 409,190,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,260,736 102,260,736 102,260,736 3,795,148,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 106,827,776 106,827,776 106,827,776 39,693,312,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,068,736 30,068,736 30,068,736 512,409,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,540,800 14,540,800 14,540,800 180,633,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,151,680 78,151,680 78,151,680 224,870,400
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,351,053,312 1,351,053,312 1,351,053,312 39,036,026,880
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 327,352,320
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 102,244,352 102,244,352 102,244,352 3,030,220,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 116,748,288 116,748,288 116,748,288 35,326,033,920
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,068,736 30,068,736 30,068,736 409,927,680
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,548,992 14,548,992 14,548,992 147,456,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,913,536 78,913,536 78,913,536 454,164,480
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,347,657,728 1,347,657,728 1,347,657,728 31,511,347,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 272,793,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#2)Working Set 94,203,904 94,203,904 94,203,904 113,049,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 117,268,480 117,268,480 117,268,480 29,594,419,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,031,872 30,031,872 30,031,872 330,547,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,561,280 14,561,280 14,561,280 126,566,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,921,728 78,921,728 78,921,728 380,928,000
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,343,746,048 1,343,746,048 1,343,746,048 26,003,865,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 233,823,086
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 118,501,376 118,501,376 118,501,376 25,683,675,429
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,031,872 30,031,872 30,031,872 283,326,171
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,561,280 14,561,280 14,561,280 108,485,486
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,635,008 78,635,008 78,635,008 252,781,714
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,339,785,216 1,339,785,216 1,339,785,216 21,862,195,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 204,595,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 120,381,440 120,381,440 120,381,440 22,896,230,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,048,256 30,048,256 30,048,256 251,596,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(rundll32)Working Set 14,626,816 14,626,816 14,626,816 109,670,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,364,672 78,364,672 78,364,672 160,358,400
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,337,192,448 1,337,192,448 1,337,192,448 18,914,508,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 181,862,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 120,696,832 120,696,832 120,696,832 20,415,283,200
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,048,256 30,048,256 30,048,256 223,641,600
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,290,944 78,290,944 78,290,944 127,795,200
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,332,838,400 1,332,838,400 1,332,838,400 16,239,329,280
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 163,676,160
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 122,019,840 122,019,840 122,019,840 18,611,896,320
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,040,064 30,040,064 30,040,064 199,802,880
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(svchost#3)Working Set 78,286,848 78,286,848 78,286,848 114,278,400
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,322,061,824 1,322,061,824 1,322,061,824 12,999,586,909
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 148,796,509
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 123,461,632 123,461,632 123,461,632 17,155,835,345
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,044,160 30,044,160 30,044,160 182,309,236
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,320,280,064 1,320,280,064 1,320,280,064 11,649,024,000
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 136,396,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 124,116,992 124,116,992 124,116,992 15,824,486,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,044,160 30,044,160 30,044,160 167,116,800
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,318,113,280 1,318,113,280 1,318,113,280 10,452,928,985
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 125,904,738
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 139,829,248 139,829,248 139,829,248 16,782,761,354
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,019,584 30,019,584 30,019,584 150,858,831
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,610,176 1,330,610,176 1,330,610,176 11,313,034,971
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 116,911,543
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 150,216,704 150,216,704 150,216,704 16,919,522,743
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,011,392 30,011,392 30,011,392 139,029,943
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,337,384,960 1,337,384,960 1,337,384,960 11,371,806,720
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(audiodg)Working Set 16,453,632 16,453,632 16,453,632 109,117,440
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 153,907,200 153,907,200 153,907,200 16,234,414,080
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 30,007,296 30,007,296 30,007,296 129,269,760
9/13/2012 4:13:11 PM – 9/13/2012 4:13:14 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,336,279,040 1,336,279,040 1,336,279,040 10,536,652,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 152,461,312 152,461,312 152,461,312 15,057,100,800
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore)Working Set 29,925,376 29,925,376 29,925,376 111,974,400
9/13/2012 4:13:14 PM – 9/13/2012 4:13:17 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,330,520,064 1,330,520,064 1,330,520,064 9,307,075,765
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 151,015,424 151,015,424 151,015,424 14,018,294,965
9/13/2012 4:13:17 PM – 9/13/2012 4:13:19 PM Condition Counter Min Avg Max Hourly Trend
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(_Total)Working Set 1,325,068,288 1,325,068,288 1,325,068,288 8,244,838,400
The working set of all processes combined is increasing at a rate greater than 100MBs per hour JTOWNSEND-VDProcess(iexplore#3)Working Set 151,126,016 151,126,016 151,126,016 13,250,560,000

Back to the top

Process % Processor Time

Description: This analysis checks all of the processes to determine if any of the processes are consuming a large amount of CPU.

If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment article in the references section for more information.

Role Specific

– Process(MSExchangeMailboxAssistants*)%Processor Time should be less than 5% of overll CPU

– Process(msftefd*)%Processor Time should be less than 10% of what the store process is consuming. Note: If indexing is running and overall CPU is greater than 80%, then msfte should backoff it’s CPU usage if that threshold is hit.

References:

Measuring .NET Application Performance

https://msdn2.microsoft.com/en-us/library/ms998579.aspx

How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment

Process(*)% Processor TimeProcess(*)% Processor TimeProcess(*)% Processor TimeProcess(*)% Processor TimeProcess(*)% Processor TimeProcess(*)% Processor TimeProcess(*)% Processor Time

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)% Processor Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/audiodg 0 1 2 100 1 0 0 0
No Thresholds JTOWNSEND-VD/conhost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/csrss#1 0 9 24 0 8 8 7 5
No Thresholds JTOWNSEND-VD/csrss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dllhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dwm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/explorer 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/googletalk 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/HorizonAgent 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#1 0 0 2 0 1 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#2 0 2 9 -800 2 1 1 1
No Thresholds JTOWNSEND-VD/iexplore#3 0 31 53 -4,200 16 28 25 24
No Thresholds JTOWNSEND-VD/iexplore 0 1 6 -600 2 0 0 0
No Thresholds JTOWNSEND-VD/lsass 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/lsm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/mmc 0 1 9 -900 2 0 0 0
No Thresholds JTOWNSEND-VD/msdtc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/MsMpEng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/msseces 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/OUTLOOK 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/pcoip_server_win32 3 30 61 0 17 27 24 22
No Thresholds JTOWNSEND-VD/rundll32 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchFilterHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchIndexer 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/services 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/smss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/spoolsv 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#10 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#2 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#3 0 1 14 1,300 3 0 0 0
No Thresholds JTOWNSEND-VD/svchost#4 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#5 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#6 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#7 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#8 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#9 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/System 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SysTrayApp 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskeng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnect 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnSvc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPVCGateway 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmtoolsd 0 0 1 100 0 0 0 0
No Thresholds JTOWNSEND-VD/VMUpgradeHelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmware-svi-ga 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareTray 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareViewClipboard 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMWVvphelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wininit 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/winlogon 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiApSrv 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm_jms 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wssm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wuauclt 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process Virtual Bytes

Description: This analysis determines if any of the processes are consuming a large of virtual memory. 32-bit processes by default are only allowed to access up to 2 GB of user mode memory. If the process becomes close to this maximum, then it could starve for memory. If a process is becoming close to it’s maximum, then consider moving the process to a 64-bit system. On 32-bit Windows and Windows Server, the /3GB switch could be used to give user mode processes up to 3 GB of addressable memory, but this takes away 1 GB of memory from the kernel which could have worse affects on the entire system such as with Pool Paged Memory and Pool Non-Paged Memory. On x64 (64-bit implementation) Windows and Windows Server, 32-bit processes that are large address aware can address up to 4 GB of virtual address space each and 64-bit processes can address up to 8 TB of virtual address space each. It is important that processes have plenty of virtual address space.

Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208Process(*)Virtual Bytes Warning Range: 6,597,069,766,656 to 8,796,093,022,208

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)Virtual Bytes Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/audiodg 51,232,768 52,822,016 53,153,792 192,102,400 691,334 52,785,152 52,739,072 52,679,826
OK JTOWNSEND-VD/conhost#1 48,250,880 48,250,880 48,250,880 0 0 48,250,880 48,250,880 48,250,880
OK JTOWNSEND-VD/conhost 23,064,576 23,064,576 23,064,576 0 0 23,064,576 23,064,576 23,064,576
OK JTOWNSEND-VD/csrss#1 95,272,960 96,628,122 96,890,880 161,792,000 518,016 96,598,926 96,562,432 96,515,511
OK JTOWNSEND-VD/csrss 47,501,312 47,537,357 47,566,848 -6,553,600 33,451 47,534,080 47,529,984 47,524,718
OK JTOWNSEND-VD/dllhost 57,860,096 57,860,096 57,860,096 0 0 57,860,096 57,860,096 57,860,096
OK JTOWNSEND-VD/dwm 83,927,040 83,927,040 83,927,040 0 0 83,927,040 83,927,040 83,927,040
OK JTOWNSEND-VD/explorer 295,780,352 295,921,254 295,981,056 -20,070,400 73,445 295,914,610 295,906,304 295,900,306
OK JTOWNSEND-VD/googletalk 199,036,928 199,036,928 199,036,928 0 0 199,036,928 199,036,928 199,036,928
OK JTOWNSEND-VD/HorizonAgent 94,203,904 95,449,088 95,514,624 0 293,086 95,441,806 95,432,704 95,421,001
OK JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/iexplore#1 443,674,624 443,674,624 443,674,624 0 0 443,674,624 443,674,624 443,674,624
OK JTOWNSEND-VD/iexplore#2 322,605,056 325,236,326 331,505,664 409,600 3,607,732 324,539,733 323,671,040 323,188,736
OK JTOWNSEND-VD/iexplore#3 160,100,352 339,351,444 388,120,576 22,513,664,000 54,763,558 333,698,711 326,774,511 318,797,351
OK JTOWNSEND-VD/iexplore 175,091,712 185,053,184 186,028,032 1,089,945,600 2,640,491 184,946,916 184,816,384 184,648,558
OK JTOWNSEND-VD/lsass 64,208,896 64,208,896 64,208,896 0 0 64,208,896 64,208,896 64,208,896
OK JTOWNSEND-VD/lsm 31,490,048 31,490,048 31,490,048 0 0 31,490,048 31,490,048 31,490,048
OK JTOWNSEND-VD/mmc 333,737,984 335,902,106 337,707,008 -396,902,400 1,903,774 335,701,561 335,450,880 335,128,576
OK JTOWNSEND-VD/msdtc 62,214,144 62,214,144 62,214,144 0 0 62,214,144 62,214,144 62,214,144
OK JTOWNSEND-VD/MsMpEng 158,765,056 158,765,056 158,765,056 0 0 158,765,056 158,765,056 158,765,056
OK JTOWNSEND-VD/msseces 109,277,184 109,277,184 109,277,184 0 0 109,277,184 109,277,184 109,277,184
OK JTOWNSEND-VD/OUTLOOK 781,021,184 781,021,184 781,021,184 0 0 781,021,184 781,021,184 781,021,184
OK JTOWNSEND-VD/pcoip_server_win32 221,552,640 221,552,640 221,552,640 0 0 221,552,640 221,552,640 221,552,640
OK JTOWNSEND-VD/rundll32 86,896,640 87,394,714 87,420,928 52,428,800 117,234 87,391,801 87,388,160 87,383,479
OK JTOWNSEND-VD/SearchFilterHost 43,065,344 43,484,774 43,589,632 52,428,800 215,163 43,473,124 43,458,560 43,439,835
OK JTOWNSEND-VD/SearchIndexer 178,855,936 180,530,381 181,088,256 210,124,800 879,227 180,468,395 180,390,912 180,291,291
OK JTOWNSEND-VD/SearchProtocolHost#1 88,289,280 88,289,280 88,289,280 0 0 88,289,280 88,289,280 88,289,280
OK JTOWNSEND-VD/SearchProtocolHost 57,806,848 71,602,586 88,289,280 3,048,243,200 15,486,811 69,748,508 67,430,912 64,451,145
OK JTOWNSEND-VD/services 33,169,408 33,667,482 33,693,696 0 117,234 33,664,569 33,660,928 33,656,247
OK JTOWNSEND-VD/smss 5,693,440 5,693,440 5,693,440 0 0 5,693,440 5,693,440 5,693,440
OK JTOWNSEND-VD/spoolsv 109,285,376 109,534,413 109,547,520 0 58,617 109,532,956 109,531,136 109,528,795
OK JTOWNSEND-VD/svchost#1 39,198,720 39,677,952 39,731,200 53,248,000 162,509 39,672,036 39,664,640 39,655,131
OK JTOWNSEND-VD/svchost#10 38,354,944 38,774,374 38,879,232 52,428,800 215,163 38,762,724 38,748,160 38,729,435
OK JTOWNSEND-VD/svchost#2 75,927,552 76,425,626 76,451,840 0 117,234 76,422,713 76,419,072 76,414,391
OK JTOWNSEND-VD/svchost#3 176,750,592 176,778,445 176,783,360 3,276,800 10,763 176,777,899 176,777,216 176,776,338
OK JTOWNSEND-VD/svchost#4 482,197,504 482,984,755 483,770,368 156,467,200 750,550 482,897,465 482,788,352 482,648,064
OK JTOWNSEND-VD/svchost#5 40,583,168 40,583,168 40,583,168 0 0 40,583,168 40,583,168 40,583,168
OK JTOWNSEND-VD/svchost#6 47,202,304 47,202,304 47,202,304 0 0 47,202,304 47,202,304 47,202,304
OK JTOWNSEND-VD/svchost#7 91,734,016 94,512,742 94,879,744 314,572,800 978,638 94,471,964 94,420,992 94,355,456
OK JTOWNSEND-VD/svchost#8 44,707,840 45,179,699 45,232,128 -52,428,800 161,372 45,173,874 45,166,592 45,157,230
OK JTOWNSEND-VD/svchost#9 29,986,816 29,986,816 29,986,816 0 0 29,986,816 29,986,816 29,986,816
OK JTOWNSEND-VD/svchost 43,085,824 43,085,824 43,085,824 0 0 43,085,824 43,085,824 43,085,824
OK JTOWNSEND-VD/System 4,706,304 4,706,304 4,706,304 0 0 4,706,304 4,706,304 4,706,304
OK JTOWNSEND-VD/SysTrayApp 206,184,448 208,019,456 208,805,888 262,144,000 1,232,502 207,932,075 207,822,848 207,682,414
OK JTOWNSEND-VD/taskeng 35,233,792 35,233,792 35,233,792 0 0 35,233,792 35,233,792 35,233,792
OK JTOWNSEND-VD/taskhost 84,279,296 84,279,296 84,279,296 0 0 84,279,296 84,279,296 84,279,296
OK JTOWNSEND-VD/TPAutoConnect 101,052,416 101,726,618 102,100,992 102,400,000 507,682 101,685,020 101,633,024 101,566,171
OK JTOWNSEND-VD/TPAutoConnSvc 61,235,200 61,864,346 62,283,776 0 527,040 61,817,742 61,759,488 61,684,590
OK JTOWNSEND-VD/TPVCGateway 56,324,096 56,324,096 56,324,096 0 0 56,324,096 56,324,096 56,324,096
OK JTOWNSEND-VD/vmtoolsd 88,686,592 89,368,166 89,735,168 0 513,132 89,327,388 89,276,416 89,210,880
OK JTOWNSEND-VD/VMUpgradeHelper 38,907,904 38,907,904 38,907,904 0 0 38,907,904 38,907,904 38,907,904
OK JTOWNSEND-VD/vmware-svi-ga 38,068,224 38,068,224 38,068,224 0 0 38,068,224 38,068,224 38,068,224
OK JTOWNSEND-VD/VMwareTray 75,571,200 76,200,346 76,619,776 0 527,040 76,153,742 76,095,488 76,020,590
OK JTOWNSEND-VD/VMwareViewClipboard 82,919,424 84,295,680 85,540,864 -131,072,000 1,308,994 84,157,326 83,984,384 83,762,030
OK JTOWNSEND-VD/VMWVvphelper 73,555,968 73,555,968 73,555,968 0 0 73,555,968 73,555,968 73,555,968
OK JTOWNSEND-VD/wininit 45,359,104 45,359,104 45,359,104 0 0 45,359,104 45,359,104 45,359,104
OK JTOWNSEND-VD/winlogon 58,978,304 58,978,304 58,978,304 0 0 58,978,304 58,978,304 58,978,304
OK JTOWNSEND-VD/WmiApSrv 37,289,984 37,289,984 37,289,984 0 0 37,289,984 37,289,984 37,289,984
OK JTOWNSEND-VD/WmiPrvSE#1 31,543,296 31,543,296 31,543,296 0 0 31,543,296 31,543,296 31,543,296
OK JTOWNSEND-VD/WmiPrvSE 46,501,888 46,501,888 46,501,888 0 0 46,501,888 46,501,888 46,501,888
OK JTOWNSEND-VD/wsnm 93,335,552 93,964,698 94,384,128 -104,857,600 527,040 93,918,094 93,859,840 93,784,942
OK JTOWNSEND-VD/wsnm_jms 793,153,536 795,040,973 796,299,264 -314,572,800 1,581,121 794,901,163 794,726,400 794,501,705
OK JTOWNSEND-VD/wssm 91,553,792 91,553,792 91,553,792 0 0 91,553,792 91,553,792 91,553,792
OK JTOWNSEND-VD/wuauclt 72,007,680 72,007,680 72,007,680 0 0 72,007,680 72,007,680 72,007,680

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process IO Data Operations/sec

Description: The rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Process(*)IO Data Operations/sec Warning Range: 1,000 to 1,299.999Process(*)IO Data Operations/sec Warning Range: 1,000 to 1,299.999Process(*)IO Data Operations/sec Warning Range: 1,000 to 1,299.999Process(*)IO Data Operations/sec Warning Range: 1,000 to 1,299.999Process(*)IO Data Operations/sec Warning Range: 1,000 to 1,299.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)IO Data Operations/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/audiodg 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/conhost#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/conhost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/csrss#1 0 10 30 -1,700 11 8 6 4
OK JTOWNSEND-VD/csrss 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/dllhost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/dwm 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/explorer 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/googletalk 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/HorizonAgent 0 0 1 0 0 0 0 0
OK JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/iexplore#1 0 0 2 0 1 0 0 0
OK JTOWNSEND-VD/iexplore#2 0 4 53 0 13 0 0 0
OK JTOWNSEND-VD/iexplore#3 0 92 518 -13,200 136 54 37 31
OK JTOWNSEND-VD/iexplore 0 3 30 -3,000 8 1 0 0
OK JTOWNSEND-VD/lsass 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/lsm 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/mmc 0 0 1 -100 0 0 0 0
OK JTOWNSEND-VD/msdtc 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/MsMpEng 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/msseces 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/OUTLOOK 0 1 2 0 1 0 0 0
OK JTOWNSEND-VD/pcoip_server_win32 0 115 166 10,800 58 109 102 93
OK JTOWNSEND-VD/rundll32 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/SearchFilterHost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/SearchIndexer 0 1 28 0 6 0 0 0
OK JTOWNSEND-VD/SearchProtocolHost#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/SearchProtocolHost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/services 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/smss 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/spoolsv 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#10 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#2 0 0 1 -100 0 0 0 0
OK JTOWNSEND-VD/svchost#3 0 0 1 0 0 0 0 0
OK JTOWNSEND-VD/svchost#4 0 0 3 -300 1 0 0 0
OK JTOWNSEND-VD/svchost#5 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#6 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#7 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#8 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#9 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/System 0 2 11 -500 3 1 0 0
OK JTOWNSEND-VD/SysTrayApp 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/taskeng 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/taskhost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/TPAutoConnect 0 0 2 0 0 0 0 0
OK JTOWNSEND-VD/TPAutoConnSvc 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/TPVCGateway 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/vmtoolsd 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/VMUpgradeHelper 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/vmware-svi-ga 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/VMwareTray 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/VMwareViewClipboard 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/VMWVvphelper 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wininit 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/winlogon 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/WmiApSrv 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/WmiPrvSE#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/WmiPrvSE 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wsnm 0 0 2 0 0 0 0 0
OK JTOWNSEND-VD/wsnm_jms 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wssm 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wuauclt 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process IO Other Operations/sec

Description: The rate at which the process is issuing I/O operations that are neither read nor write operations (for example, a control function). This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Process(*)IO Other Operations/sec Warning Range: 1,000 to 1,646Process(*)IO Other Operations/sec Warning Range: 1,000 to 1,646Process(*)IO Other Operations/sec Warning Range: 1,000 to 1,646Process(*)IO Other Operations/sec Warning Range: 1,000 to 1,646Process(*)IO Other Operations/sec Warning Range: 1,000 to 1,646Process(*)IO Other Operations/sec Warning Range: 1,000 to 1,646

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)IO Other Operations/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/audiodg 0 154 203 19,900 74 148 141 132
OK JTOWNSEND-VD/conhost#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/conhost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/csrss#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/csrss 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/dllhost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/dwm 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/explorer 0 2 13 -400 4 1 0 0
OK JTOWNSEND-VD/googletalk 0 24 48 -3,800 20 21 19 16
OK JTOWNSEND-VD/HorizonAgent 0 0 1 0 0 0 0 0
OK JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/iexplore#1 0 1 14 0 3 0 0 0
OK JTOWNSEND-VD/iexplore#2 0 3 25 -1,000 6 1 0 0
This process is using more than 1000 data I/O’s (network or disk) per second JTOWNSEND-VD/iexplore#3 0 219 1,646 -78,200 422 94 40 27
OK JTOWNSEND-VD/iexplore 0 10 130 -4,800 31 0 0 0
OK JTOWNSEND-VD/lsass 0 0 2 0 0 0 0 0
OK JTOWNSEND-VD/lsm 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/mmc 0 3 53 -5,300 12 0 0 0
OK JTOWNSEND-VD/msdtc 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/MsMpEng 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/msseces 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/OUTLOOK 0 0 1 0 0 0 0 0
This process is using more than 1000 data I/O’s (network or disk) per second JTOWNSEND-VD/pcoip_server_win32 23 562 1,082 -6,300 360 509 454 389
OK JTOWNSEND-VD/rundll32 11 13 14 0 0 13 13 13
OK JTOWNSEND-VD/SearchFilterHost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/SearchIndexer 0 12 112 -700 26 5 3 1
OK JTOWNSEND-VD/SearchProtocolHost#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/SearchProtocolHost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/services 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/smss 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/spoolsv 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#10 0 0 2 0 0 0 0 0
OK JTOWNSEND-VD/svchost#2 0 7 64 0 17 2 0 0
OK JTOWNSEND-VD/svchost#3 0 1 6 -400 2 0 0 0
OK JTOWNSEND-VD/svchost#4 0 3 48 -4,800 11 1 0 0
OK JTOWNSEND-VD/svchost#5 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#6 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#7 0 3 23 -400 5 2 1 1
OK JTOWNSEND-VD/svchost#8 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost#9 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/svchost 0 0 9 -900 2 0 0 0
OK JTOWNSEND-VD/System 0 1 2 -200 1 1 0 0
OK JTOWNSEND-VD/SysTrayApp 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/taskeng 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/taskhost 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/TPAutoConnect 0 2 42 0 10 0 0 0
OK JTOWNSEND-VD/TPAutoConnSvc 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/TPVCGateway 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/vmtoolsd 0 16 133 13,300 39 2 2 2
OK JTOWNSEND-VD/VMUpgradeHelper 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/vmware-svi-ga 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/VMwareTray 0 3 5 500 2 2 2 2
OK JTOWNSEND-VD/VMwareViewClipboard 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/VMWVvphelper 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wininit 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/winlogon 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/WmiApSrv 1 2 2 0 0 2 2 2
OK JTOWNSEND-VD/WmiPrvSE#1 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/WmiPrvSE 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wsnm 0 0 2 0 1 0 0 0
OK JTOWNSEND-VD/wsnm_jms 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wssm 0 0 0 0 0 0 0 0
OK JTOWNSEND-VD/wuauclt 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
This process is using more than 1000 data I/O’s (network or disk) per second JTOWNSEND-VDProcess(iexplore#3)IO Other Operations/sec 1,646 1,646 1,646 388,350
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
This process is using more than 1000 data I/O’s (network or disk) per second JTOWNSEND-VDProcess(pcoip_server_win32)IO Other Operations/sec 1,082 1,082 1,082 352,440

Back to the top

Process ID Process

Description: ID Process is the unique identifier of this process. ID Process numbers are reused, so they only identify a process for the lifetime of that process.

Process(*)ID ProcessProcess(*)ID ProcessProcess(*)ID ProcessProcess(*)ID ProcessProcess(*)ID ProcessProcess(*)ID Process

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)ID Process Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/audiodg 2,276 2,276 2,276 0 0 2,276 2,276 2,276
No Thresholds JTOWNSEND-VD/conhost#1 684 684 684 0 0 684 684 684
No Thresholds JTOWNSEND-VD/conhost 1,556 1,556 1,556 0 0 1,556 1,556 1,556
No Thresholds JTOWNSEND-VD/csrss#1 2,904 2,904 2,904 0 0 2,904 2,904 2,904
No Thresholds JTOWNSEND-VD/csrss 380 380 380 0 0 380 380 380
No Thresholds JTOWNSEND-VD/dllhost 2,572 2,572 2,572 0 0 2,572 2,572 2,572
No Thresholds JTOWNSEND-VD/dwm 1,784 1,784 1,784 0 0 1,784 1,784 1,784
No Thresholds JTOWNSEND-VD/explorer 848 848 848 0 0 848 848 848
No Thresholds JTOWNSEND-VD/googletalk 3,168 3,168 3,168 0 0 3,168 3,168 3,168
No Thresholds JTOWNSEND-VD/HorizonAgent 1,976 1,976 1,976 0 0 1,976 1,976 1,976
No Thresholds JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#1 2,552 2,552 2,552 0 0 2,552 2,552 2,552
No Thresholds JTOWNSEND-VD/iexplore#2 3,816 3,816 3,816 0 0 3,816 3,816 3,816
No Thresholds JTOWNSEND-VD/iexplore#3 5,000 5,000 5,000 0 0 5,000 5,000 5,000
No Thresholds JTOWNSEND-VD/iexplore 3,024 3,024 3,024 0 0 3,024 3,024 3,024
No Thresholds JTOWNSEND-VD/lsass 544 544 544 0 0 544 544 544
No Thresholds JTOWNSEND-VD/lsm 552 552 552 0 0 552 552 552
No Thresholds JTOWNSEND-VD/mmc 3,796 3,796 3,796 0 0 3,796 3,796 3,796
No Thresholds JTOWNSEND-VD/msdtc 2,656 2,656 2,656 0 0 2,656 2,656 2,656
No Thresholds JTOWNSEND-VD/MsMpEng 820 820 820 0 0 820 820 820
No Thresholds JTOWNSEND-VD/msseces 2,940 2,940 2,940 0 0 2,940 2,940 2,940
No Thresholds JTOWNSEND-VD/OUTLOOK 2,956 2,956 2,956 0 0 2,956 2,956 2,956
No Thresholds JTOWNSEND-VD/pcoip_server_win32 3,712 3,712 3,712 0 0 3,712 3,712 3,712
No Thresholds JTOWNSEND-VD/rundll32 4,880 4,880 4,880 0 0 4,880 4,880 4,880
No Thresholds JTOWNSEND-VD/SearchFilterHost 1,176 1,176 1,176 0 0 1,176 1,176 1,176
No Thresholds JTOWNSEND-VD/SearchIndexer 2,824 2,824 2,824 0 0 2,824 2,824 2,824
No Thresholds JTOWNSEND-VD/SearchProtocolHost#1 4,204 4,204 4,204 0 0 4,204 4,204 4,204
No Thresholds JTOWNSEND-VD/SearchProtocolHost 3,364 3,742 4,204 84,000 429 3,691 3,626 3,544
No Thresholds JTOWNSEND-VD/services 528 528 528 0 0 528 528 528
No Thresholds JTOWNSEND-VD/smss 272 272 272 0 0 272 272 272
No Thresholds JTOWNSEND-VD/spoolsv 1,692 1,692 1,692 0 0 1,692 1,692 1,692
No Thresholds JTOWNSEND-VD/svchost#1 744 744 744 0 0 744 744 744
No Thresholds JTOWNSEND-VD/svchost#10 2,680 2,680 2,680 0 0 2,680 2,680 2,680
No Thresholds JTOWNSEND-VD/svchost#2 896 896 896 0 0 896 896 896
No Thresholds JTOWNSEND-VD/svchost#3 936 936 936 0 0 936 936 936
No Thresholds JTOWNSEND-VD/svchost#4 960 960 960 0 0 960 960 960
No Thresholds JTOWNSEND-VD/svchost#5 332 332 332 0 0 332 332 332
No Thresholds JTOWNSEND-VD/svchost#6 688 688 688 0 0 688 688 688
No Thresholds JTOWNSEND-VD/svchost#7 1,140 1,140 1,140 0 0 1,140 1,140 1,140
No Thresholds JTOWNSEND-VD/svchost#8 1,916 1,916 1,916 0 0 1,916 1,916 1,916
No Thresholds JTOWNSEND-VD/svchost#9 2,392 2,392 2,392 0 0 2,392 2,392 2,392
No Thresholds JTOWNSEND-VD/svchost 668 668 668 0 0 668 668 668
No Thresholds JTOWNSEND-VD/System 4 4 4 0 0 4 4 4
No Thresholds JTOWNSEND-VD/SysTrayApp 1,712 1,712 1,712 0 0 1,712 1,712 1,712
No Thresholds JTOWNSEND-VD/taskeng 3,996 3,996 3,996 0 0 3,996 3,996 3,996
No Thresholds JTOWNSEND-VD/taskhost 1,136 1,136 1,136 0 0 1,136 1,136 1,136
No Thresholds JTOWNSEND-VD/TPAutoConnect 1,960 1,960 1,960 0 0 1,960 1,960 1,960
No Thresholds JTOWNSEND-VD/TPAutoConnSvc 1,428 1,428 1,428 0 0 1,428 1,428 1,428
No Thresholds JTOWNSEND-VD/TPVCGateway 1,408 1,408 1,408 0 0 1,408 1,408 1,408
No Thresholds JTOWNSEND-VD/vmtoolsd 996 996 996 0 0 996 996 996
No Thresholds JTOWNSEND-VD/VMUpgradeHelper 1,360 1,360 1,360 0 0 1,360 1,360 1,360
No Thresholds JTOWNSEND-VD/vmware-svi-ga 1,796 1,796 1,796 0 0 1,796 1,796 1,796
No Thresholds JTOWNSEND-VD/VMwareTray 2,488 2,488 2,488 0 0 2,488 2,488 2,488
No Thresholds JTOWNSEND-VD/VMwareViewClipboard 3,356 3,356 3,356 0 0 3,356 3,356 3,356
No Thresholds JTOWNSEND-VD/VMWVvphelper 2,432 2,432 2,432 0 0 2,432 2,432 2,432
No Thresholds JTOWNSEND-VD/wininit 424 424 424 0 0 424 424 424
No Thresholds JTOWNSEND-VD/winlogon 2,248 2,248 2,248 0 0 2,248 2,248 2,248
No Thresholds JTOWNSEND-VD/WmiApSrv 2,668 2,668 2,668 0 0 2,668 2,668 2,668
No Thresholds JTOWNSEND-VD/WmiPrvSE#1 2,112 2,112 2,112 0 0 2,112 2,112 2,112
No Thresholds JTOWNSEND-VD/WmiPrvSE 1,292 1,292 1,292 0 0 1,292 1,292 1,292
No Thresholds JTOWNSEND-VD/wsnm 1,192 1,192 1,192 0 0 1,192 1,192 1,192
No Thresholds JTOWNSEND-VD/wsnm_jms 1,368 1,368 1,368 0 0 1,368 1,368 1,368
No Thresholds JTOWNSEND-VD/wssm 3,000 3,000 3,000 0 0 3,000 3,000 3,000
No Thresholds JTOWNSEND-VD/wuauclt 3,208 3,208 3,208 0 0 3,208 3,208 3,208

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process IO Read Operations/sec

Description: The rate at which the process is issuing read I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Process(*)IO Read Operations/secProcess(*)IO Read Operations/secProcess(*)IO Read Operations/secProcess(*)IO Read Operations/secProcess(*)IO Read Operations/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)IO Read Operations/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/audiodg 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/csrss#1 0 10 30 -1,700 11 8 6 4
No Thresholds JTOWNSEND-VD/csrss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dllhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dwm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/explorer 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/googletalk 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/HorizonAgent 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#2 0 4 53 0 13 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#3 0 49 317 -10,400 96 21 5 0
No Thresholds JTOWNSEND-VD/iexplore 0 1 14 -1,400 3 0 0 0
No Thresholds JTOWNSEND-VD/lsass 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/lsm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/mmc 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/msdtc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/MsMpEng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/msseces 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/OUTLOOK 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/pcoip_server_win32 0 109 157 10,800 55 104 97 89
No Thresholds JTOWNSEND-VD/rundll32 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchFilterHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchIndexer 0 1 15 0 3 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/services 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/smss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/spoolsv 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#10 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#2 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#3 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#4 0 0 3 -300 1 0 0 0
No Thresholds JTOWNSEND-VD/svchost#5 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#6 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#7 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#8 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#9 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/System 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SysTrayApp 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskeng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnect 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnSvc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPVCGateway 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmtoolsd 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMUpgradeHelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmware-svi-ga 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareTray 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareViewClipboard 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMWVvphelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wininit 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/winlogon 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiApSrv 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm_jms 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wssm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wuauclt 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process IO Write Operations/sec

Description: The rate at which the process is issuing write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Process(*)IO Write Operations/secProcess(*)IO Write Operations/secProcess(*)IO Write Operations/secProcess(*)IO Write Operations/secProcess(*)IO Write Operations/secProcess(*)IO Write Operations/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)IO Write Operations/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/audiodg 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/csrss#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/csrss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dllhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dwm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/explorer 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/googletalk 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/HorizonAgent 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/Idle 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#1 0 0 2 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#2 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#3 0 43 201 -2,800 57 29 18 13
No Thresholds JTOWNSEND-VD/iexplore 0 2 16 -1,600 4 1 0 0
No Thresholds JTOWNSEND-VD/lsass 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/lsm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/mmc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/msdtc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/MsMpEng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/msseces 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/OUTLOOK 0 0 2 0 1 0 0 0
No Thresholds JTOWNSEND-VD/pcoip_server_win32 0 5 14 0 4 4 3 3
No Thresholds JTOWNSEND-VD/rundll32 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchFilterHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchIndexer 0 1 13 0 3 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/services 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/smss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/spoolsv 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#10 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#2 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#3 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#4 0 0 2 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#5 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#6 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#7 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#8 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#9 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/System 0 2 11 -500 3 1 0 0
No Thresholds JTOWNSEND-VD/SysTrayApp 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskeng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnect 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnSvc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPVCGateway 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmtoolsd 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMUpgradeHelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmware-svi-ga 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareTray 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareViewClipboard 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMWVvphelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wininit 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/winlogon 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiApSrv 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm_jms 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wssm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wuauclt 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Process % Privileged Time

Description: % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

Process(*)% Privileged TimeProcess(*)% Privileged TimeProcess(*)% Privileged TimeProcess(*)% Privileged TimeProcess(*)% Privileged TimeProcess(*)% Privileged TimeProcess(*)% Privileged Time

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Process(*)% Privileged Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/audiodg 0 0 2 100 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/conhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/csrss#1 0 9 24 0 8 8 7 5
No Thresholds JTOWNSEND-VD/csrss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dllhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/dwm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/explorer 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/googletalk 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/HorizonAgent 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#1 0 0 2 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#2 0 1 3 -200 1 0 0 0
No Thresholds JTOWNSEND-VD/iexplore#3 0 9 17 -700 5 8 7 7
No Thresholds JTOWNSEND-VD/iexplore 0 1 5 -500 1 0 0 0
No Thresholds JTOWNSEND-VD/lsass 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/lsm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/mmc 0 0 2 -200 0 0 0 0
No Thresholds JTOWNSEND-VD/msdtc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/MsMpEng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/msseces 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/OUTLOOK 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/pcoip_server_win32 0 3 6 100 2 2 2 2
No Thresholds JTOWNSEND-VD/rundll32 0 0 1 -100 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchFilterHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchIndexer 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SearchProtocolHost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/services 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/smss 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/spoolsv 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#10 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#2 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#3 0 0 4 400 1 0 0 0
No Thresholds JTOWNSEND-VD/svchost#4 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#5 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#6 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#7 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#8 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost#9 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/svchost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/System 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/SysTrayApp 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskeng 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/taskhost 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnect 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPAutoConnSvc 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/TPVCGateway 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmtoolsd 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMUpgradeHelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/vmware-svi-ga 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareTray 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMwareViewClipboard 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/VMWVvphelper 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wininit 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/winlogon 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiApSrv 0 0 1 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE#1 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/WmiPrvSE 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wsnm_jms 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wssm 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/wuauclt 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Processor

Processor % Processor Time

Description: % Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the duration of the idle thread is active in the sample interval, and subtracting that time from interval duration. This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. % Processor Time is the sum of % User Time and % Privileged Time unless there is hardware involvement in the form of interupts and/or DPCs.

This analysis creates a Warning alert for utilization greater than 50% on any processor and creates a critical alert for utilization greater than 80%.

If average processor utilization is high based on the thresholds witin this analysis, then check if it is high user mode CPU or high privileged mode. If high privileged mode CPU is suspected, then see the Privileged Mode CPU Analysis. If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment article in the references section for more information.

References:

Processor(*)% Processor Time Warning Range: 50 to 80 Critical Range: 80 to 100Processor(*)% Processor Time Warning Range: 50 to 80 Critical Range: 80 to 100

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor(*)% Processor Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
More than 80% Processor Utilization JTOWNSEND-VD/_Total 5 77 100 -1,900 30 74 71 67
More than 80% Processor Utilization JTOWNSEND-VD/0 5 77 100 -1,900 30 74 71 67

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:26 PM – 9/13/2012 4:12:29 PM Condition Counter Min Avg Max Hourly Trend
More than 50% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 57 57 57 23,400
More than 50% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 57 57 57 23,400
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 91 91 91 42,300
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 91 91 91 42,300
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 82 82 82 22,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 82 82 82 22,800
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 24,750
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 24,750
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 19,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 19,800
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 100 100 100 16,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 100 100 100 16,800
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 14,143
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 14,143
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 100 100 100 12,600
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 100 100 100 12,600
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 83 83 83 7,800
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 83 83 83 7,800
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 96 96 96 9,360
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 96 96 96 9,360
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 99 99 99 9,000
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 99 99 99 9,000
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 91 91 91 7,050
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 91 91 91 7,050
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 98 98 98 7,477
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 98 98 98 7,477
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
More than 50% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 69 69 69 3,214
More than 50% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 69 69 69 3,214
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
More than 80% Processor Utilization JTOWNSEND-VDProcessor(_Total)% Processor Time 92 92 92 5,760
More than 80% Processor Utilization JTOWNSEND-VDProcessor(0)% Processor Time 92 92 92 5,760

Back to the top

Processor % Privileged Time

Description: This counter indicates the percentage of time a thread runs in privileged mode also known as kernel mode. When your application calls operating system functions (for example to perform file or network I/O or to allocate memory), these operating system functions are executed in privileged mode.

High privileged mode CPU indicates that computer is spending too much time in system I/O versus real (user mode) work. % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

This analysis throws a warning alert if privileged mode CPU is consuming more than 20% of total CPU and a critical alert if consuming More than 30% of total CPU.

Next steps

The CPU consumption might be caused by another busy resource such as network, memory, or disk I/O. High privileged mode CPU can also by caused by high amounts of Context Switches/second. See the High Context Switches/second analysis. The KernRate (KrView) tool can be used to profile the kernel to see what component is consuming the most kernel resources. To see more information about how KernRate can be used to analyze high priviledge mode CPU problems, see Mark Russinovich’s blog entry in the references section below.

References:

Processor(*)% Privileged Time Warning Range: 20 to 30 Critical Range: 30 to 99.999Processor(*)% Privileged Time Warning Range: 20 to 30 Critical Range: 30 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor(*)% Privileged Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VD/_Total 2 25 44 -1,100 13 23 20 18
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VD/0 2 25 44 -1,100 13 23 20 18

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 27 27 27 4,050
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 27 27 27 4,050
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 38 38 38 7,200
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 38 38 38 7,200
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 39 39 39 6,300
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 39 39 39 6,300
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 44 44 44 6,686
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 44 44 44 6,686
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 40 40 40 4,950
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 40 40 40 4,950
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 22 22 22 800
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 22 22 22 800
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 32 32 32 2,520
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 32 32 32 2,520
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 39 39 39 3,436
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 39 39 39 3,436
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 29 29 29 1,650
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 29 29 29 1,650
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 39 39 39 2,908
More than 30% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 39 39 39 2,908
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 22 22 22 514
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 22 22 22 514
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(_Total)% Privileged Time 21 21 21 360
More than 20% privileged (kernel) mode CPU usage JTOWNSEND-VDProcessor(0)% Privileged Time 21 21 21 360

Back to the top

Processor % Interrupt Time

Description: % Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. A dramatic increase in this counter indicates potential hardware problems.

This analysis checks for % Interrupt Time greater than 30%. If this occurs, then consider updating devices drivers for hardware that correlates to this alert.

References:

Measuring .NET Application Performance

https://msdn2.microsoft.com/en-us/library/ms998579.aspx

Processor(*)% Interrupt Time Warning Range: 30 to 50 Critical Range: 50 to 99.999Processor(*)% Interrupt Time Warning Range: 30 to 50 Critical Range: 50 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor(*)% Interrupt Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/_Total 0 0 2 100 0 0 0 0
OK JTOWNSEND-VD/0 0 0 2 100 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Processor % DPC Time

Description: % DPC Time is the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval. DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a component of % Privileged Time because DPCs are executed in privileged mode. They are counted separately and are not a component of the interrupt counters. This counter displays the average busy time as a percentage of the sample time.

Processor(*)% DPC Time Warning Range: 20 to 99.999Processor(*)% DPC Time Warning Range: 20 to 99.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor(*)% DPC Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD/_Total 0 0 2 0 1 0 0 0
OK JTOWNSEND-VD/0 0 0 2 0 1 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Processor % User Time

Description: % User Time is the percentage of elapsed time the processor spends in the user mode. User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems. The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory. The operating system switches application threads to privileged mode to access operating system services. This counter displays the average busy time as a percentage of the sample time.

This analysis provides statistics only. Threads running on a processor will be in either user mode measured using % User Time or in priviledge/kernel mode measured using % Privileged Time. High % User Time indicates a high amount of application code is being executed. This is desirable versus too much time in privileged mode. See the Processor % Privileged Time analysis for more information.

Processor(*)% User TimeProcessor(*)% User Time

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor(*)% User Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 4 52 74 -800 21 50 47 44
No Thresholds JTOWNSEND-VD/0 4 52 74 -800 21 50 47 44

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Processor DPC Rate

Description: DPC Rate is the rate at which deferred procedure calls (DPCs) were added to the processors DPC queues between the timer ticks of the processor clock. DPCs are interrupts that run at alower priority than standard interrupts. Each processor has its own DPC queue. This counter measures the rate that DPCs were added to the queue, not the number of DPCs in the queue. This counter displays the last observed value only; it is not an average.

Processor(*)DPC Rate Warning Range: 10 to 20 Critical Range: 20 to 29.999Processor(*)DPC Rate Warning Range: 10 to 20 Critical Range: 20 to 29.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor(*)DPC Rate Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 0 9 21 0 6 8 7 6
No Thresholds JTOWNSEND-VD/0 0 9 21 0 6 8 7 6

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Processor Information

Processor Information Parking Status

Description: Parking Status represents whether a processor is parked or not.

Processor Information(*)Parking StatusProcessor Information(*)Parking Status

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor Information(*)Parking Status Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/0,_Total 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/0,0 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Processor Information % of Maximum Frequency

Description: % of Maximum Frequency is the percentage of the current processor’s maximum frequency.

Processor Information(*)% of Maximum FrequencyProcessor Information(*)% of Maximum Frequency

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition Processor Information(*)% of Maximum Frequency Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/0,_Total 0 0 0 0 0 0 0 0
No Thresholds JTOWNSEND-VD/0,0 100 100 100 0 0 100 100 100

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Server

Server Pool Nonpaged Failures

Description: The number of times allocations from nonpaged pool have failed. Indicates that the computer’s physical memory is too small.

ServerPool Nonpaged Failures

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition ServerPool Nonpaged Failures Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Server Pool Paged Failures

Description: The number of times allocations from paged pool have failed. Indicates that the computer’s physical memory or paging file are too small.

ServerPool Paged Failures

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition ServerPool Paged Failures Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

System

System Processor Queue Length

Description: Processor Queue Length (PQL) is the number of threads in the processor queue. Unlike the disk counters, this counter shows ready threads only, not threads that are running. There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent of the workload.

This analysis determines if the average processor queue length exceeds the number of processors. If so, then this could indicate a processor bottleneck. Use this analysis in correlation with Privileged Mode CPU Analysis and Excessive Processor Use by Process analysis.

Note: Due to the way in which this counter is collected, ignore this counter and alerts for it when collected from a virtual computer.

If there are more tasks ready to run than there are processors, threads queue up. The processor queue is the collection of threads that are ready but not able to be executed by the processor because another active thread is currently executing. A sustained or recurring queue of more threads than number of processors is a good indication of a processor bottleneck.

You can use this counter in conjunction with the Processor% Processor Time counter to determine if your application can benefit from more CPUs.

Reference:

SystemProcessor Queue Length Warning Range: 1.999 to 23 Critical Range: 9.999 to 23

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition SystemProcessor Queue Length Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
More than 10 ready threads are queued for each processor JTOWNSEND-VD 2 9 23 0 6 7 6 5

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:29 PM – 9/13/2012 4:12:32 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 9 9 9 6,300
9/13/2012 4:12:32 PM – 9/13/2012 4:12:35 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 8 8 8 3,600
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 3 3 3 450
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 10 10 10 2,880
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 3 3 3 300
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 10 10 10 2,057
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 13 13 13 2,475
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 18 18 18 3,200
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 9 9 9 1,260
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 15 15 15 2,127
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 12 12 12 1,500
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
More than 2 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 10 10 10 1,108
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 23 23 23 2,700
9/13/2012 4:13:11 PM – 9/13/2012 4:13:14 PM Condition Counter Min Avg Max Hourly Trend
More than 10 ready threads are queued for each processor JTOWNSEND-VDSystemProcessor Queue Length 15 15 15 1,462

Back to the top

System High Context Switching

Description:
Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another. Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service. It is the sum of ThreadContext Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches. There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

High context switching is only a problem if overall CPU is high as well. This analysis checks for high CPU, high privileged mode CPU, and high system context switches per sec.

Threshold: As a general rule, context switching rates of greater than 5,000 per second per processor are considered a warning. If context switching rates exceed 10,000 per second per processor, then there is a constraint.

Significance: Context switching happens when a higher priority thread preempts a lower priority thread that is currently running or when a high priority thread blocks. High levels of context switching can occur when many threads share the same priority level. This often indicates that there are too many threads competing for the processors on the system. If you do not see much processor utilization and you see very low levels of context switching, it could indicate that threads are blocked.

Reference:

Measuring .NET Application Performance

https://msdn2.microsoft.com/en-us/library/ms998579.aspx

SystemContext Switches/sec Warning Range: 2,499.999 to 8,454 Critical Range: 4,999.999 to 9,999.999

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition SystemContext Switches/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 4,206 6,656 8,454 196,400 987 6,452 6,290 6,165

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
Time Range
9/13/2012 4:12:26 PM – 9/13/2012 4:12:29 PM Condition Counter Min Avg Max Hourly Trend
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,526 6,526 6,526 4,176,000
9/13/2012 4:12:35 PM – 9/13/2012 4:12:38 PM Condition Counter Min Avg Max Hourly Trend
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,775 7,775 7,775 1,606,050
9/13/2012 4:12:38 PM – 9/13/2012 4:12:41 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 8,337 8,337 8,337 1,487,160
9/13/2012 4:12:41 PM – 9/13/2012 4:12:44 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,036 7,036 7,036 849,000
9/13/2012 4:12:44 PM – 9/13/2012 4:12:47 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,550 7,550 7,550 859,886
9/13/2012 4:12:47 PM – 9/13/2012 4:12:50 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,179 7,179 7,179 668,925
9/13/2012 4:12:50 PM – 9/13/2012 4:12:53 PM Condition Counter Min Avg Max Hourly Trend
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 5,749 5,749 5,749 308,600
9/13/2012 4:12:53 PM – 9/13/2012 4:12:56 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,449 6,449 6,449 403,740
9/13/2012 4:12:56 PM – 9/13/2012 4:12:59 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,704 6,704 6,704 408,764
9/13/2012 4:12:59 PM – 9/13/2012 4:13:02 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 8,454 8,454 8,454 637,200
9/13/2012 4:13:02 PM – 9/13/2012 4:13:05 PM Condition Counter Min Avg Max Hourly Trend
More than 5,000 Context Switches/sec per processor, more than 30% ratio of privileged to total CPU, and more than 70% total processor time or more than 20,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 6,644 6,644 6,644 337,569
9/13/2012 4:13:05 PM – 9/13/2012 4:13:08 PM Condition Counter Min Avg Max Hourly Trend
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 7,031 7,031 7,031 363,214
9/13/2012 4:13:08 PM – 9/13/2012 4:13:11 PM Condition Counter Min Avg Max Hourly Trend
More than 2,500 Context Switches/sec per processor, more than 20% ratio of privileged to total CPU, and more than 50% total processor time or more than 10,000 Context Switches/sec JTOWNSEND-VDSystemContext Switches/sec 5,751 5,751 5,751 185,400

Back to the top

System System Calls/sec

Description: System Calls/sec is the combined rate of calls to operating system service routines by all processes running on the computer. These routines perform all of the basic scheduling and synchronization of activities on the computer, and provide access to non-graphic devices, memory management, and name space management. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

SystemSystem Calls/sec

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition SystemSystem Calls/sec Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 16,243 26,347 38,529 -1,760,000 6,311 25,043 23,928 22,999

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

TCPv4

TCPv4 Connection Failures

Description: Connection Failures is the number of times TCP connections have made a direct transition to the CLOSED state from the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.

TCPv4Connection Failures

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition TCPv4Connection Failures Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
OK JTOWNSEND-VD 9 9 9 0 0 9 9 9

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

VM Memory

Memory Active in MB

Description: Amount of memory that is actively used by the virtual machine, as estimated by VMkernel based on recently touched memory pages.

A large delta between memory active and vRAM allocated could indicate over-sized VM’s. Consider reducing memory allocation to VM’s and monitor.
See https://www.vmware.com/files/pdf/perf-vsphere-memory_management.pdf for information on how VMware manages memory!!!

VM MemoryMemory Active in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Active in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 491 517 552 6,100 23 513 508 504

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Ballooned in MB

Description: The amount of memory that has been reclaimed from this virtual machine via the VMware Memory Balloon mechanism.

When VMware tools are installed on a virtual machine they provide device drivers into the host virtualization layer, from within the guest operating system. Part of this package that is installed is the balloon driver or “vmmemctl” which can be observed inside the guest. The balloon driver communicates to the hypervisor to reclaim memory inside the guest when it is no longer valuable to the operating system. If the Physical ESX server begins to run low on memory it will grow the balloon driver to reclaim memory from the guest. This process reduces the chance that the physical ESX host will begin to swap, which you will cause performance degradation.

Ballooning indicates that your ESXi hosts have some memory contention. In general, a little bit of ballooning is not bad. Ballooning at a low level allows ESXi to reclaim inactive memory pages from guest VM’s. However, if there are not enough inactive pages to claim, active pages may be reclaimed. This can hurt performance of the guest VM.

Resolution

  • Verify Distributed Resource Scheduler is enabled on your cluster. DRS can redistribute VM’s from over-subscribed hosts to less busy hosts.
  • Install more memory in physical hosts.
  • Change the power policy of VMware View pools to suspend or power-off to conserve host resources. Note: this is at the expense of increased logon times for users.
  • Add additional hosts to cluster. Note configuration maximums of 8 hosts per cluster in older versions of vSphere and View when using VMFS-based Linked Clones.
  • Reduce the amount of memory given to View desktops. Review the Memory Active in MB counter (above). If memory active is substantially below configured memory, reduce the amount of memory given to desktops. Recommended starting values are 2GB for XP, 2GB for Win7 x86 and 3GB for Win7 x64.

See https://www.virtualinsanity.com/index.php/2010/02/19/performance-troubleshooting-vmware-vsphere-memory/ for more.

VM MemoryMemory Ballooned in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Ballooned in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Limit in MB

Description: The maximum amount of memory that is allowed to the virtual machine. Assigning a Memory Limit ensures that this virtual machine never consumes more than a certain amount of the allowed memory. By limiting the amount of memory consumed, a portion of this shared resource is allowed to other virtual machines.

In vSphere, it’s possible to set memory limits that define a maximum quantity of memory a VM is allowed to consume. You might want to set such limits to protect physical memory from being over-consumed by a memory-hungry VM.
However, if you don’t plan carefully, setting a VM memory limit can have an unexpected impact on VM performance. That impact occurs because the VM is unaware that a limit has been placed upon it. A limited VM with 4GB of assigned vRAM operates under the assumption that it has its full memory assignment. As it attempts to use more memory than its limit, that memory must come from ballooning or swapping. Either of these actions can incur a performance tax on the host, which can impact the performance of other VMs on that host.

It’s generally not a good idea to set memory limits on VMs. Instead, you should adjust downward the quantity of vRAM assigned to that VM.

The Memory Limit value shown below should be equal to the amount of vRAM allocated to your View desktop. If the value is less than vRAM assigned, you are limited.

VM MemoryMemory Limit in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Limit in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 2,048 2,048 2,048 0 0 2,048 2,048 2,048

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Mapped in MB

Description: The mapped memory size of this virtual machine. This is the current total amount of guest memory that is backed by physical memory. Note that this number may include pages of memory shared between multiple virtual machines and thus may be an overestimate of the amount of physical host memory *consumed* by this virtual machine.

VM MemoryMemory Mapped in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Mapped in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 2,048 2,048 2,048 0 0 2,048 2,048 2,048

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Overhead in MB

Description: The amount of overhead memory associated with this virtual machine consumed on the host system. Once a virtual machine is powered on the ESX host reserves memory for the the normal operations of VMware infrastructure. This memory can’t be used for swapping or ballooning, and is reserved for the system. Bigger VM’s require more overhead to run.

See this page for vSphere 5 overhead values: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.resmgmt.doc_50%2FGUID-B42C72C1-F8D5-40DC-93D1-FB31849B1114.html

If you chronically oversize your VM’s, the overhead consumed will increase. This leads to a less efficient datacenter and reduced resources for running VM’s as overhead memory cannot be shared, swapped or ballooned. Right-size your VM’s.

VM MemoryMemory Overhead in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Overhead in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 118 118 118 0 0 118 118 118

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Reservation in MB

Description: The minimum amount of memory that is guaranteed to the virtual machine. Assigning a Memory Reservation ensures that even as other virtual machines on the same host consume memory, there is still a certain minimum amount for this virtual machine.

Reservations may be used in View environments to reduce the footprint of VM’s on disk as reserved memory is included in the .vswap file written to disk for each VM.

A small reservation on the parent VM can also help ensure that each VM in the pool has at least a little bit of vRAM to work in heavily oversubscribed environments. Take care to not over reserve resources in your environment – do not reserve 100% of memory for each View desktop.

Starting values for View desktop reservations might be around 10%. For example, If reserving 10% of a 2GB desktop, our vswap is reduced by 205MB per desktop. On a 200 desktop deployment, this can lead to 41GB disk savings (205mb * 200). 205mb reserved memory will probably be enough to keep a Windows desktop running (barely) even if all other memory is ballooned or swapped out if you failed to plan and over-over-subscribed your environment.

Note: This example 41GB of disk savings will be lost to reserved ESXi host RAM across the cluster. You will not be able to use this host RAM, even if the VM’s with reserved memory are totally idle. This can exacerbate problems caused by oversubscription. To mitigate this impact, consider setting your View pools where you have set a reservation to have a powered-off power policy. A suspend power policy will consume disk space, negating the savings you were trying to achieve by reserving memory.

VM MemoryMemory Reservation in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Reservation in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Shared in MB

Description: The amount of physical memory associated with this virtual machine that is copy-on-write (COW) shared on the host.

Sharing is good!

In View environments, most running VM’s will share a common image, especially with Linked Clone pools where all VM’s are running against a common base disk.

Read more about Transparent Page Sharing (TPS) in View environemnts here: https://myvirtualcloud.net/?p=1797 and here: https://myvirtualcloud.net/?p=2545.

When multiple virtual machines are running, some of them may have identical sets of memory content. This presents opportunities for sharing memory across virtual machines (as well as sharing within a single virtual machine). For example, several virtual machines may be running the same guest operating system, have the same applications, or contain the same user data. With page sharing,the hypervisor can reclaim the redundant copies and only keep one copy, which is shared by multiple virtual machines in the hostphysical memory. As a result, the total virtual machine host memory consumption is reduced and a higher level of memory overcommitment is possible.

In ESXi, the redundant page copies are identified by their contents. This means that pages with identical content can be shared regardless of when, where, and how those contents are generated. ESX scans the content of guest physical memory for sharing opportunities. Instead of comparing each byte of a candidate guest physical page to other pages, an action that is prohibitively expensive, ESX uses hashing to identify potentially identical pages.

VM MemoryMemory Shared in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Shared in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 299 305 314 -1,500 6 304 302 302

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Shared Saved in MB

Description: The estimated amount of physical memory on the host saved from copy-on-write (COW) shared guest physical memory.

This shows the total amount of memory saved on the particular host this VM was running on. More is better. If this value is near zero (0), investigate your host configuration.

Review https://myvirtualcloud.net/?p=1328 for information on tuning TPS settings to drive higher levels of memory sharing per host.

VM MemoryMemory Shared Saved in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Shared Saved in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 204 210 219 -1,500 6 209 208 207

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Shares

Description: The number of memory shares allocated to the virtual machine.

This value alone is not significant. Shares must be considered across all VM’s on the host, cluster, and resource pool, if used. If the VM with performance problems has a lower number of shares (or is in a resource pool with a lower number of shares, or oversubscribed shares (https://vmtoday.com/2012/03/vmware-vsphere-resource-pools-resource-allocation-revisited/) than other VM’s it may suffer performance degradation in environments where there is resource contention and/or memory oversubscription.

Shares play an important role in determining the allocation targets when memory is overcommitted. When the hypervisor needs memory, it reclaims memory from the virtual machine that owns the fewest shares-per-allocated page.

A significant limitation of the pure proportional-share algorithm is that it does not incorporate any information about the actual memory usage of the virtual machine. As a result, some idle virtual machines with high shares can retain idle memory unproductively, while some active virtual machines with fewer shares suffer from the lack of memory.

ESX resolves this problem by estimating a virtual machine’s working set size and charging a virtual machine more for the idle memory than for the actively used memory through an idle tax. A virtual machine’s shares-per-allocated page ratio is adjusted to be lower if a fraction of the virtual machine’s memory is idle. Hence, memory will be reclaimed preferentially from the virtual machines that are not fully utilizing their allocated memory. The detailed algorithm can be found in Memory Resource Management in VMware ESX Server.

VM MemoryMemory Shares

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Shares Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 20,480 20,480 20,480 0 0 20,480 20,480 20,480

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Swapped in MB

Description: The amount of memory associated with this virtual machine that has been swapped by ESX.

If this is much above zero for an active machine you’ve got problems. TPS and Ballooning have failed to provide sufficient memory for the host to use for other running VM’s because you are oversubscribed, so ESXi is now swapping to disk. Swapping is a slow operation and causes severe degradation of guest performance.

Resolution

  • Verify Distributed Resource Scheduler is enabled on your cluster. DRS can redistribute VM’s from over-subscribed hosts to less busy hosts.
  • Install more memory in physical hosts.
  • Change the power policy of VMware View pools to suspend or power-off to conserve host resources. Note: this is at the expense of increased logon times for users.
  • Add additional hosts to cluster. Note configuration maximums of 8 hosts per cluster in older versions of vSphere and View when using VMFS-based Linked Clones.
  • Reduce the amount of memory given to View desktops. Review the Memory Active in MB counter (above). If memory active is substantially below configured memory, reduce the amount of memory given to desktops. Recommended starting values are 2GB for XP, 2GB for Win7 x86 and 3GB for Win7 x64.

VM MemoryMemory Swapped in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Swapped in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Memory Used in MB

Description: The estimated amount of physical host memory currently consumed for this virtual machine’s physical memory. This is the same as ‘Memory Mapped in MB’ – ‘Memory Shared Saved in MB’.

VM MemoryMemory Used in MB

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM MemoryMemory Used in MB Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD 1,828 1,837 1,843 1,500 6 1,836 1,835 1,834

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

VM Processor

Limit in MHz

Description: The maximum processing power in MHz allowed to the virtual machine. Assigning a CPU Limit ensures that this virtual machine never consumes more than a certain amount of the available processor power. By limiting the amount of processing power consumed, a portion of the processing power becomes available to other virtual machines.

From VMware KB 1033115: When a CPU Limit is set on a virtual machine resource settings, the virtual machine is deliberately held from being scheduled to a PCPU when it has used up its allocated CPU resource. This happens regardless of the CPU utilization. If the limit is set to 500MHz, the virtual machine is descheduled from the PCPU and has to wait before it is allowed to be scheduled again. As such, the virtual machine might experience performance degradation.

Note: For an SMP virtual machine, the sum of all vCPUs cannot exceed the specified limit. For example, 4 vCPU virtual machine with a limit of 1200MHz and equal load among vCPUs would result in a max of 300MHz per vCPU.

Translated, this means that we’re not slowing down the pCPU for this VM – that’s not possible. What we are doing is basically artificially introducing CPU Ready (for more on CPU Ready see here: https://vmtoday.com/2010/08/high-cpu-ready-poor-performance/) for the VM.

If the value shown here is less than the ‘Host Processor Speed in MHz’ value, you are limited. The default for VM’s is ‘unlimited’, which should appear as some unwieldy number in the range of terahertz or petahertz (not that your servers can do this).

VM Processor(*)Limit in MHz

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)Limit in MHz Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 4,294,967,295 4,294,967,295 4,294,967,295 0 0 4,294,967,295 4,294,967,295 4,294,967,295

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Reservation in MHz

Description: The minimum processing power in MHz available to the virtual machine. Assigning a CPU Reservation ensures that even as other virtual machines on the same host consume shared processing power, there is still a certain minimum amount for this virtual machine.

See https://www.yellow-bricks.com/2010/07/08/reservations-primer/ and https://frankdenneman.nl/2010/06/reservations-and-cpu-scheduling/for more info on reservations.

In general, you should not be setting a reservation for Veiw desktops. There may be some unique use cases for reserving CPU for high-profile users’ desktops (CEO, CTO, your own admin console) in View. Do this sparingly, as reservations can limit the ESXi scheduler and make your virtual datacenter inefficient. CPU Reservations can introduce higher CPU ready for VM’s without reservations. Reservations may not solve CPU Ready issues for the VM’s they are set on either (https://joshodgers.com/2012/07/22/common-mistake-using-cpu-reservations-to-solve-cpu-ready/

VM Processor(*)Reservation in MHz

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)Reservation in MHz Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Shares

Description: The number of CPU shares allocated to the virtual machine.

Each virtual machine is granted a number of CPU shares. The more shares a virtual machine has, the more often it gets a time slice of a CPU when there is no CPU idle time. Shares represent a relative metric for allocating CPU capacity.

This value alone is not significant. Shares must be considered across all VM’s on the host, cluster, and resource pool, if used. If the VM with performance problems has a lower number of shares (or is in a resource pool with a lower number of shares, or oversubscribed shares (https://vmtoday.com/2012/03/vmware-vsphere-resource-pools-resource-allocation-revisited/) than other VM’s it may suffer performance degradation in environments where there is resource contention and/or memory oversubscription.

Read this VMware PDF for a deep-dive into CPU Scheduling: https://www.vmware.com/files/pdf/techpaper/VMW_vSphere41_cpu_schedule_ESX.pdf

If this value is variable (not a flat line), this may indicate that your VM is in a resource pool configured with a set number of shares. As your View environment dynamically spins up and down VM’s within the pool, the percentage of shares for a particular machine will vary. Understand the impact of shares, reservations and limits on VMs and Resource Pools!!!!

VM Processor(*)Shares

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)Shares Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 1,000 1,000 1,000 0 0 1,000 1,000 1,000

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

CPU stolen time

Description: The time (in ms) that the VM was runnable but not scheduled to run.

This is CPU Ready!!!

For more on CPU Ready see: https://vmtoday.com/2010/08/high-cpu-ready-poor-performance/

CPU Ready is often a sign of over subscribing CPU resources or over-sizing your virtual machines. This counter shows CPU Ready time as a percentage per milisecond that the CPU was ready to run but could not be scheduled by the ESXi Scheduler. Multiply by 100 to get percentage of CPU Ready. In general, anything above 10% CPU Ready will result in poor performance.

For more on Scheduling/Time Keeping in VM’s see: https://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf. Also see the vSphere Performance Monitoring Guide here: https://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf

If this counter is in a warning or critical state, check CPU Ready for the host that this VM is running on in vCenter. The value in the realtime graph is a summation of miliseconds VM’s were ready but could not be scheduled. Divide the value shown in the vCenter ESXi Performance tab by the number of milisecond timeslices in the graph (realtime graph = 20 second refresh = 20000 slices). Example: If CPU ready is 5200 on the CPU/RealTime graph, divide 5200/20000 = .26 x 100 = 26% CPU RDY. Also check ESXTOP on the ESXi host that this VM is running on. If multiple VM’s show high CPU ready, you are over-provisioning VM’s with too many vCPU’s or have too high of a consolidation ration (too many VM’s per host). Remove vCPU’s or add additional pCPU’s or hosts.

VM Processor(*)CPU stolen time

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)CPU stolen time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 0 0 0 0 0 0 0 0

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

% Processor Time

Description: Current load of the VM’s virtual processor(s).

This is the amount of time that the CPU is active. If the VM is using vSMP, this is the aggregate average of all CPU’s in the VM.

If this value is regularly over 70%, you may benefit from adding an additional vCPU. Be aware, however, that an additional CPU multiplied over all VM’s may drive CPU Ready upwards, negatively impacting performance.

VM Processor(*)% Processor Time

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)% Processor Time Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 13 66 108 -2,500 28 61 57 53

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Effective VM Speed in MHz

Description: The approximate average effective speed of the VM’s virtual CPU over the time period between the two samples.

Remember, A VM’s vCPU cannot go any faster than the speed of a single core/thread of the physical CPU that’s backing it.

VM Processor(*)Effective VM Speed in MHz

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)Effective VM Speed in MHz Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 271 1,799 2,765 -48,700 839 1,700 1,592 1,461

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Host processor speed in MHz

Description: Host Processor speed.

This is the clock speed of the physical processor backing the VM. If this value fluxuates, it could be due to a couple issues:

1.) vMotion of VM between hosts with different physical hardware. Best practice for VMware vSphere clusters suggests maintaining hosts with identical hardare configurations to prevent unpredictable performance as VM’s are vMotioned from host to host. Identical host configuration may also help VMware vSphere Distributed Resource Scheduler recommend best placement for VM’s.

2.) Power Management settings – if your host is configured with active/dynamic power management in BIOS. Consider setting a static ‘High Performance’ power management profile or disable power management in BIOS. See this VMware KB for more info: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018206

VM Processor(*)Host processor speed in MHz

Overall Counter Instance Statistics

Overall statistics of each of the counter instances. Min, Avg, and Max are the minimum, average, and Maximum values in the entire log. Hourly Trend is the calculated hourly slope of the entire log. 10%, 20%, and 30% of Outliers Removed is the average of the values after the percentage of outliers furthest away from the average have been removed. This is to help determine if a small percentage of the values are extreme which can skew the average.
Condition VM Processor(*)Host processor speed in MHz Min Avg Max Hourly Trend Std Deviation 10% of Outliers Removed 20% of Outliers Removed 30% of Outliers Removed
No Thresholds JTOWNSEND-VD/_Total 2,800 2,800 2,800 0 0 2,800 2,800 2,800

Alerts

An alert is generated if any of the thresholds were broken during one of the time ranges analyzed. The background of each of the values represents the highest priority threshold that the value broke. See each of the counter’s respective analysis section for more details about what the threshold means.
No Alerts Found

Back to the top

Back to the top

Disclaimer: This report was generated using the Performance Analysis of Logs (PAL) tool. The information provided in this report is provided “as-is” and is intended for information purposes only. The software is licensed “as-is”. You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

Reader Interactions

Trackbacks

Drop a comment below:

This site uses Akismet to reduce spam. Learn how your comment data is processed.