Documentation
Limitations
The restrictions described below are necessary for reasons of performance and security of the system. It is not planned to change these.
| Limitation | Description |
|---|---|
| Maximum number of objects | 50000. The address space of 10000-59999 is used. Depending on the license/IP-Symcon version, this value may be lower. |
| Maximum size of a string variable | Over 1024kb an error is generated and the content is not written. For reasons of performance and stability, data over 8kb should be transferred elsewhere. The 1024kb limit simply serves as a hard limit in order to contain catastrophic effects during runtime due to faulty scripts. |
| Maximum size of the RegisterVariable Buffer | For size 8kb and above a warning is written in the log. Only the last 64kb of data is kept in the buffer. Older data will be discarded without further warning. |
| Maximum size of the Cutter Buffer | For size 8kb and above a warning is written in the log. Only the last 64kb of data is kept in the buffer. Older data will be discarded without further warning. |
| Maximum number of PHP-Threads | The default setting of 50 PHP threads is completely sufficient for almost all systems. The minimum is 25 PHP threads. If a value lower than 25 is selected, 25 PHP threads will still be created. If more PHP threads are required, the value can be increased to 100, for example. Much higher values make little sense in most cases and consume an unnecessary amount of RAM. |
| Maximum memory per PHP thread | The default setting is 32MB per PHP thread. This value can be changed to a maximum of 64M per thread in the php.ini file. Consult the PHP documentation for this. |
| Maximum memory per buffer | The buffer has a soft limit of 256kB and a hard limit of 1024kB. This means that IP-Symcon throws a "warning" in the messages if the buffer is larger than 256kB and the maximum size of the buffer is 1024kB. Data larger than 1024kB will be truncated. |
| Query of data via AC_*functions | A maximum of 10000 lines are returned, regardless of whether the limit was selected higher. No warning is given. Queries should be optimized accordingly so that the aggregated data can be accessed. This minimizes the load on the database and thus also minimizes access times for the WebFront visualization of the individual accesses. |
| Maximum associations per variable profile | A maximum of 128 (since 5.0; previously 32) associations are allowed per variable profile. The reasoning to this is that every change to the profile associations must be transferred to all WebFronts, which results in a high overhead if there are a large number of associations. In addition, this feature is not designed for e.g. a playlist selection, as this would negatively influence the design and layout of the WebFront. |