Monitoring Application Performance on the .NET Compact Framework Part VII - Version 2 performance counters (Part V: JIT Compiler counters)

Today's post is the fifth in the series of .NET Compact Framework v2 performance counters.  For a complete listing of the previous installments, please see the list below.

Pre-requisite:
Monitoring Application Performance on the .NET Compact Framework Part I - Enabling performance counters
.NET Compact Framework Version 1:
Monitoring Application Performance on the .NET Compact Framework Part II - Version 1 performance counters
.NET Compact Framework Version 2:
Monitoring Application Performance on the .NET Compact Framework Part III - Version 2 performance counters (Part I: Loader counters)
Monitoring Application Performance on the .NET Compact Framework Part IV - Version 2 performance counters (Part II: Generics counters)
Monitoring Application Performance on the .NET Compact Framework Part V - Version 2 performance counters (Part III: Locks and Threads counters)
Monitoring Application Performance on the .NET Compact Framework Part VI - Version 2 performance counters (Part IV: Garbage Collector counters)

The following table lists all of the performance counters available in version 2 of the .NET Compact Framework.  The counters highlighted, in yellow, are the ones I will be talking about today.

The statistics file includes running totals, the most recent value (last datum), count (n), average (mean), minimum and maximum values for the counters. I've included an example file at the end of this post. For counters where a given column is not relevant, a hyphen (-) is logged.

I will use the following format to describe each counter.
Counter name
Brief description of the counter
Discussion of the contents of relevant columns (total, last datum, n, mean, min, max)
Any additional comments relating to the counter

JIT Compiler Counters
The counters discussed below relate to the .NET Compact Framework's Just-In-Time (JIT) compiler.

Native Bytes Jitted
The size (in bytes) of the native code generated by the JIT compler.
total: Running total of the number of bytes compiledd
last datum: Size of last compilation
n: Number of methods compiled
mean: Average compilation size per method
min: Size of smallest method compilation
max: Size of largest method compilation

Methods Jitted
The number of methods compiled by the JIT compiler.
total: Running count of compiled methods

Bytes Pitched
The size (in bytes) of the JIT compiled code which has been removed from the JIT Heap.
total: Running total of bytes pitched
last datum: Size of last pitching
n: Number of times code was pitched
mean: Average number of bytes pitched
min: The fewest number of bytes pitched
max: The largest number of bytes pitched

Methods Pitched
The number of methods, which have been compiled by the JIT compiler, that have been removed from the JIT Heap.
total: Running count of pitched methods
Unless your application was moved to the background during it's runtime, any value for the Methods Pitched counter indicates the application ran under memory pressure.

Method Pitch Latency Time (ms)
The total time (in milliseconds) spent pitching methods from the JIT Heap.
total: Running total of the time spent pitching code
last datum: Time spent during the most recent code pitch
n: Number of times code was pitched
mean: The average length of in which time a code pitch was performed
min: The briefest amount of time spent pitching code
max: The longest amount of time spent pitching code

Example statistics file
I have highlighted the counters discussed here with a yellow background.

Up next: Exception, Interop and Networking counters.

Take care,
-- DK

Disclaimer(s):
This posting is provided "AS IS" with no warranties, and confers no rights.