Requirements and Limitations

The IP.21 Server component supports Aspen InfoPlus.21 version 10.1 and newer, given that the following requirements are met:

Hardware Requirements

  • For the IP.21 Server service, 2GB of free RAM on the InfoPlus.21 system host are required.

  • Namespace Browsing in the range of 50,000-100,000 IP.21 records is supported, provided that the involved systems fulfill the following hardware requirements:

    Component Host CPU RAM Hard Disk

    system

    2.90 GHz Quad-Core

    32GB

    500GB

    IP.21 Source

    2.90 GHz Quad-Core

    32GB

    500GB

Configuration Requirements for the InfoPlus.21 System

When the AspenTech Inmation IP.21 Server is used as a gRPC Server or as the source for replication, the IP.21 Publisher Task ('TSK_PUBR'; from ReplicationPublisherNG.exe) needs to be disabled in the InfoPlus.21 Manager.

The AspenTech Inmation IP.21 Server service receives data from the IP.21 system as part of the IP.21 Replication Queue. Therefore, on the IP.21 side (i.e. in the Aspen InfoPlus.21 Administrator app), it is necessary to ensure that all relevant data is sent to the Replication Queue.

The data which the IP.21 system sends to the Replication Queue can be controlled on record level as well as on tag field level:

  • For a record to be sent to the Replication Queue, the checkbox for Enable Tag Replication in the Replication tab of the record’s properties needs to be selected.

  • For a tag field to be included in a record sent to the Replication Queue, the Publish Updates property for this field needs to be set to YES in the record’s parent definition record.

    It may take up to an hour before the changes on IP.21 Definition Records become apparent in the inmation system as the InfoPlus.21 caches them for up to one hour before applying them to the child records.

Limitations

The IP.21 Server service is subject to the following limitations:

  • Only one IP.21 Server service can be installed on the host machine of the InfoPlus.21 system. Installing multiple instances may lead to unexpected behavior and data-loss.

  • For the Replication functionality, the destination IP21 system needs to have a sufficient amount of free tags and memory to contain the source IP21 system’s tags. Otherwise CREATE_TAG replication messages can’t be processed and will lead to a loss of data.

  • The InfoPlus.21 system does not immediately apply changes on IP.21 Definition Records to the child records but once per hour. Therefore it might take up to an hour before the changes become apparent in the inmation system.

When replicating values from the IP_TREND_VALUE field, Aspen InfoPlus.21 version 11 and newer is required. Earlier versions do not support timestamp publishing for these fields.

Performance Information

Subscription Performance

As an estimation of performance, the Datasource IP.21 gRPC has the capacity for 50,000-100,000 IP.21 records updating per second on the following standard hardware:

Component Host CPU RAM Hard Disk

system

2.90 GHz, 4 vCPU

32GB

500GB

IP.21 Source

2.90 GHz, 4 vCPU

32GB

500GB

This is a broad estimation of the performance limitations and should only be used for guidance, actual results are specific to on the user’s system, network, use cases and other components installed.

For achieving maximum throughput between a gRPC Datasource and an AspenTech Inmation IP.21 server component, a low-latency communication line should be used (i.e. LAN networks). Using WAN connections will reduce the throughput significantly. This is especially relevant for internal API requests, such as they for example used in History Transporter configurations.

Secure Replication Performance

As an estimation of performance for secure replication, the IP.21 Server has the capacity for 50,000-100,000 IP.21 tags updating per second on the following standard hardware:

Component Host CPU RAM Hard Disk

Node (system)

2.90 GHz, 8 vCPU

32GB

512GB

IP.21 Source

2.90 GHz, 8 vCPU

16GB

512GB

IP.21 Target

2.90 GHz, 8 vCPU

16GB

512GB

The maximum performance and capacity for secure replication is achieved if archiving (IP_ARCHIVING) is set to OFF for both the IP.21 Source and IP.21 Target machines. The performance may be altered when archiving is set to ON.

IP.21 History Transfer Performance

As an estimation of performance, History Transporter with the IP.21 gPRC Datasource has the capacity to transfer all data specified in the test parameters, with the following standard hardware, under the conditions specified in the test parameters:

Reference architecture with 3 hosts, and local area network:

Component Host CPU RAM Hard Disk

system

2.90 GHz, 8 vCPU

32GB

500GB

IP.21 gRPC Datasource Node

2.90 GHz, 8 vCPU

16GB

500GB

IP.21 System with IP21 Server Node

2.90 GHz, 8 vCPU

16GB

500GB

Test parameters:

History Transporter Objects 1 6

Tags per Transporter

3000

500

Update Rate for all tags

1000 ms

1000 ms

Data points for single tag, in the tested time frame

100000 points

100000 points

Duration to complete

3 hours

1 hour
This is a broad estimation of the performance limitations and should only be used for guidance, actual results are specific to the user’s system, network, use cases and other components installed.

IP.21 Guaranteed Delivery Mode Performance

As an estimation of performance, IP.21 Server Node, with the IP.21 gPRC Datasource in Guaranteed Delivery Mode has the capacity to transfer all data specified in the test parameters, with the following standard hardware, under the conditions specified in the test parameters:

Reference architecture with 3 hosts, and local area network:

Component Host CPU RAM Hard Disk

system

2.90 GHz, 8 vCPU

32GB

500GB

IP.21 gRPC Datasource Node

2.90 GHz, 8 vCPU

16GB

500GB

IP.21 System with IP21 Server Node

2.90 GHz, 8 vCPU

16GB

500GB

Test parameters:

  • Data Points refer to actual samples generated by tags (i.e. 10.000 tags that deliver a new point each second would generate 10 million total data points in 1000 seconds)

  • Buffer Drain Time refers to a how long it takes the IP.21 Datasource object to transfer all changes that have accumulated during an outage between IP.21 Server Node (IP.21 System) and IP.21 gRPC Datasource Node.

Total Data Points 10 Million 20 Million 50 Million

Buffer Drain Time

6 minutes

9 minutes

24 minutes

Average Drain Rate

30,000 pts / sec

30,000 pts / sec

30,000 pts / sec
This is a broad estimation of the performance limitations and should only be used for guidance, actual results are specific to the user’s system, network, use cases and other components installed.