Você está na página 1de 2

31/01/2018 3226OSI8 - What are recommended Exception and Compression settings

OSIsoft Home PI Square Community Learning Live Library Welcome, Guest Sign In

Search All OSIsoft

My Support Contact Us Resources Downloads Products

Was this information helpful? Yes No Partially Open Case

Knowledge Base Article

3226OSI8 - What are recommended Exception and Compression settings

Product: PI Data Archive

Version(s): Any

English ▼

What are the recommended compression and exception settings?

Settings for exception reporting and compression testing allow you to tune PI points for maximum efficiency. Exception reporting affects the flow of
data from the interface node to the server for a point, and compression testing affects the efficiency of data storage in the archive for a point.

PI Data Archive can store enormous amounts of data, but it is important to store meaningful data. Storing excessive data in the PI Data Archive
affects performance. When clients make calls to retrieve compressed data or execute summary calculations over large periods of time, much of
the archive data will likely be read from disk the first time the call is made. This is an expensive operation compared to reading from memory. If
only meaningful data is stored in archives, greater time ranges of data can be stored in memory (read cache) for quicker access.


Exception reporting
Exception reporting takes place on the interface node before the value is sent to the PI Data Archive. This process filters out noise, which reduces
the communication (I/O) burden between the PI Data Archive and the interface node.

OSIsoft recommends setting exception deviation to a value slightly less than the precision of the instrument. Another guideline is to set Exception
Deviation (ExcDev) to half the Compression Deviation (CompDev).
Exception Maximum (ExcMax): Maximum time span between exceptions, expressed in seconds.
Exception Minimum (ExcMin): Minimum time span between exceptions, expressed in seconds.
Exception Deviation (ExcDev): The ExcDev attribute specifies how much a value may differ from the previous value before it is
considered to be a significant value. This is a dead band that, when exceeded, causes an exception. You can specify exception
deviation for a PI point using either the ExcDev or ExcDevPercent attribute.

Compression testing
The snapshot subsystem performs compression testing on PI Data Archive to enhance data storage efficiency and conserve disk
space. However, if you are using the PI Buffer Subsystem, compression is performed on the interface node before the data is sent to the PI Data
Archive (or fanned to multiple PI Data Archives, in the case of PI Collective).

Your goal is to set compression to store data efficiently without sacrificing its accuracy. More efficient data storage can capture longer periods of
on-line data on the same disk space and enable faster analysis and data retrieval. The idea here is not to store an event that PI can essentially
recreate by extrapolation of surrounding events.

To check your compression ratio, you can use either the "piartool -ss" command from the pi\adm command prompt(1), or check the ratio of the
following two PI performance counters in the Windows Performance monitor(2):

(1) "Snapshot Events" : "Events Sent to Queue"

(2) PI Snapshot Subsystem counters:

"Snapshot/sec : "Queued Events/sec"

Ideally, this ratio should be between 10:1 to 100:1, meaning for every 10-100 events that come into the queue, one is sent to the archive.
Minimally, it should be between 3:1 to 10:1, especially on systems with a larger point count (over 50,000 points) or systems with very high

https://techsupport.osisoft.com/Troubleshooting/KB/3226OSI8 1/2
31/01/2018 3226OSI8 - What are recommended Exception and Compression settings
frequency data.

If the ratio is 1:1 to 2:1, it is likely the system is very inefficient with archive disk usage for a given time period.

Turning compression off

Turning compression off is not recommended. However, it is appropriate for laboratory or manually entered points or totalized points, where each
event is significant. If you set Compressing to 0 (OFF) all exceptions are archived (no compression).

An alternative to turning compression off is to set the Compressing attribute to 1(ON), and the Compression Deviation (CompDev) attribute to 0
(OFF). In this case, successive identical values (or values aligning perfectly along a line) are not archived. This is much more efficient in terms of
archive use than turning compression off.

For example, if a value of "High" is sent to the archive followed by another "High" value, the second value is not added. As another example, if a
sequence of values "1", "2", "3", "4" occur at even time intervals, the 2 and 3 are not archived because their values can be calculated from the
slope between 1 and 4.

Note: In the case of Compressing=1 and CompDev=0 with a very small deviation over a very long period of time, it is possible that a slightly
deviating event will not be archived because the compression slope is so small.

"CompMin" and "CompMax"

"CompMin" and "CompMax" are limits that refer to the time between events in the archive. A new event is not recorded if the time since the last
recorded event is less than the compression minimum time for the point.

Additional Resources

OSIsoft YouTube Video – Exception and compression quick summary

OSIsoft YouTube Video – Exception and compression full details
PI Live Library – PI Data Archive – Exception reporting and compression testing
PI Data Archive System Management Guide

Article ID: 3226OSI8 Created: 2006-04-27

Article Type: Informational Last Updated: 2017-08-14

Enabling Operational Intelligence

Privacy Legal Copyright Contact Us

https://techsupport.osisoft.com/Troubleshooting/KB/3226OSI8 2/2