Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Data Archive Reference

Data Archive localhost statistics

  • Last UpdatedJul 15, 2025
  • 3 minute read

The table shows some basic performance counters that are useful in monitoring Data Archive. These points contain performance information about the Data Archive server as well as the machine that runs it.

  • The performance counters for the machine are useful in determining resource problems of the machine that runs Data Archive.

  • The performance counters for the Data Archive server are useful in determining how well the Data Archive server is performing.

    Tag

    Description

    PERF.LOCALHOST.Logical Disk(_Total).Free Megabytes

    Free Megabytes displays the unallocated space on the disk drive in MB. One MB = 1,048,576 bytes.

    PERF.LOCALHOST.Memory.% Committed Bytes In Use

    % Committed Bytes In Use is the ratio of Memory: Committed Bytes to Memory: Commit Limit. (Committed memory is physical memory in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is determined by the size of the paging file. 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.

    PERF.LOCALHOST.Memory.Page Faults/sec

    Page Faults/sec is the overall rate that faulted pages are handled by the processor. It is measured in numbers of pages faulted per second. A page fault occurs when a process requires code or data that is not in its working set (its space in physical memory). This counter includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory). Most processors can handle large numbers of soft faults without consequence. However, hard faults can cause significant delays. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.

    PERF.LOCALHOST.Processor(0).% Processor Time

    % Processor Time is the percentage of time that the processor is executing a non-Idle thread. This counter was designed as a primary indicator of processor activity. It is calculated by measuring the time that the processor spends executing the thread of the Idle process in each sample interval, and subtracting that value from 100%. (Each processor has an Idle thread, which consumes cycles when no other threads are ready to run). It can be viewed as the percentage of the sample interval spent doing useful work. This counter displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time the service was inactive, and then subtracting that value from 100%.

    PERF.LOCALHOST.TCP.Segments Retransmitted/sec

    Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.

    PERF.LOCALHOST.TCP.Segments Sent/sec

    Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.

    PERF.LOCALHOST.Process(piarchss).% Processor Time PERF.LOCALHOST.Process(pibasess).% Processor Time PERF.LOCALHOST.Process(pinetmgr).% Processor Time PERF.LOCALHOST.Process(pisnapss).% Processor Time

    % Processor Time is the percentage of elapsed time that all of the threads of this process used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count. On Multi-processor machines the maximum value of the counter is 100 % times the number of processors.

    PERF.LOCALHOST.PI Archive.Read Events operations/sec

    Rate of archive events read.

    PERF.LOCALHOST.PI Archive.Cache Record Disk Reads/sec

    Archive cache disk reads.

    PERF.LOCALHOST.PI Archive.Cache Record Memory Reads/sec

    Archive cache memory hits.

    PERF.LOCALHOST.PI Base Subsystem.Point Count

    Total number of defined points. This number includes the Connector Point Count.

    PERF.LOCALHOST.PI Network Manager(_Total).Connections

    The number of connections to PI Network Manager. This counter only applies to instance _Total.

    PERF.LOCALHOST.PI Network Manager(_Total).Messages Sent/sec PERF.LOCALHOST.PI Network Manager(piarchss).Messages Sent/sec PERF.LOCALHOST.PI Network Manager(pibasess).Messages Sent/sec PERF.LOCALHOST.PI Network Manager(pisnapss).Messages Sent/sec

    The number of messages sent to PI Network Manager.

    PERF.LOCALHOST.PI Snapshot.OutOfOrderSnapshots/sec

    Out of order events sent to the snapshot.

    PERF.LOCALHOST.PI Snapshot.Queued Events/sec

    Events sent to the event queue.

    PERF.LOCALHOST.PI Snapshot.Snapshots/sec

    Events sent to the snapshot.

    PERF.LOCALHOST.PI Update-Manager.Pending events

    Total Events pending in the PIUpdate Manager database.

    PERF.LOCALHOST.CALCULATED.PI Compression Ratio

    PI Compression Ratio is a performance equation that calculates amount of data that is compressed.

    PERF.LOCALHOST.CALCULATED.PI Archive.Cache Hit Rate

    PI Archive.Cache Hit Rate is a performance equation that measures the rate at which data is accessed from memory as opposed to disk.

TitleResults for “How to create a CRG?”Also Available in