View the Performance of a Data Store

Procedure

  1. Access Configuration Hub.
  2. In the NAVIGATION section, under the Configuration Hub plugin for Historian, select Datastores. Alternatively, you can select Systems, right-click the system in which the data store is available (or select ), and then select Browse Data Stores.
    The Data Stores section appears.
  3. Right-click the data store whose performance you want to access (or select ), and then select View Data Store Performance.
    The performance of the data store appears, displaying the following information.
    Field Description
    ARCHIVE COMPRESSION The current effect of archive data compression. If the value is zero, it indicates that archive compression is either ineffective or disabled. To increase the effect of data compression, increase the value of archive compression deadbands on individual tags.

    In calculating the effect of archive compression, Historian counts internal system tags as well as data source tags. Therefore, when working with a very small number of tags and with compression disabled on data source tags, this field may indicate a value other than zero. If you use a realistic number of tags, however, system tags will constitute a very small percentage of total tags and will therefore not cause a significant error in calculating the effect of archive compression on the total system.
    WRITE CACHE HIT The hit ratio of the write cache in percentage of total writes. It is a measure of how efficiently the system is collecting data. Typically, this value should range from 95 to 99.99%. If the data is changing rapidly over a wide range, however, the hit percentage drops significantly because current values differ from recently cached values. More regular sampling may increase the hit percentage. Out-of-order data also reduces the hit ratio.
    RECEIVE RATE Indicates how busy the server is at a given instance and the rate at which the server is receiving data from collectors.
    FREE SPACE Indicates how much disk space (in MB) is left in the current archive.
    CONSUMPTION RATE Indicates how fast the archive disk space is consumed. If the value is too high, you can reduce it by slowing the poll rate on selected tags or data points or by increasing the filtering on the data (widening the compression deadband to increase compression).
    EST. DAYS TO FULL Indicates how much time is left before the archive is full, based on the current consumption rate. This value is dynamically calculated by the server and becomes more accurate as an archive file gets closer to completion. This value is only an estimate and will vary based on a number of factors, including the current compression effectiveness. The system sends messages notifying you at 5, 3, and 1 days until full. After the archive is full, a new archive must be created (can be automatic or manual).

    To increase this value, you must reduce the consumption rate. To ensure that collection is not interrupted, make sure that the Automatically Create Archives option is enabled.

    You may also want to enable the Overwrite Old Archives option if you have limited disk capacity. Enabling this option, however, means that some old data will be lost when new data overwrites the data in the oldest online archive. Use this feature only when necessary.
    FAILED WRITES Indicates the number of samples that failed to be written. Since failed writes are a measure of system malfunctions or an indication of offline archive problems, this value should be zero. If you observe a non-zero value, investigate the cause of the problem and take corrective action.

    Historian also generates a message if a write fails. Note that the message only appears once per tag, for a succession of failed writes associated with that tag. For example, if the number displayed in this field is 20, but they all pertain to one Historian tag, you will only receive one message until that Historian tag is functional again.
    ALERTS SINCE STARTUP

    Indicates a count of system warnings or alerts generated since the last startup. A high value here may indicate a problem of some kind. You should review the alerts and determine the probable cause. The count resets to zero on restart. The message database, however, may contain more alerts than this value.
    MESSAGE SINCE STARTUP Displays a count of system messages generated since the last startup. The system resets the value to zero on restart. The message database, however, may contain more messages than this value.