Performance issues, Performance issues -13, 7 performance issues – Echelon i.LON 100 e2 Internet Server User Manual
Page 43
![background image](/manuals/735745/43/background.png)
LON 100 Internet Server Programmer’s Reference
4-13
4.7 Performance Issues
The
i.
LON 100 contains 32 MB of RAM, which allows for complicated application
configurations and extensive network use. However, even with this amount of memory, it is
still possible for very high levels of network traffic to the
i.
LON 100, especially using the
SOAP interface, to eventually exhaust its memory. This could result in delays in network
access of the
i.
LON 100, performance problems for the
i.
LON 100 applications, or in the
worst case even a reboot of the
i.
LON 100.
If your
i.
LON 100 exhibits some of these symptoms, you should consider reducing the level of
network traffic to it. The following numbers are guidelines that apply to the use of the
i.
LON
100’s SOAP interface. While they are not absolute limits or guarantees of performance, they
may be helpful to follow when attempting to manage the
i.
LON 100’s network traffic load or
troubleshoot a performance problem.
As a result, you should follow these guidelines when programming SOAP applications:
• Limit the number of data points referenced in a single Get or Read message to no more
than 100. For more information, see Chapter 5, Data Server.
• Limit the number of alarm log records read in a single message to no more than 100. For
more information on reading alarm log records, see AlarmNotifierRead on page 8-20.
• Limit the number of data log records read in a single message to no more than 150. For
more information on reading data log records, see DataLoggerRead on page 6-11.
• If the combined XML file sizes for a given application exceed 100 KB, don’t try to read all
the configuration data for that application in a single Get message. This could potentially
happen with the Event Scheduler application if all of its functional blocks were used, or
possibly with the Alarm Notifier application.
• Don’t send a request message larger than 100 KB. Some possible examples of this might
be defining more than 100 NVL points in the Data Server in a single message with
DataServerSet, or writing to 40 Alarm Notifiers in a single message with
AlarmNotifierSet.
•
Limit the number of simultaneous SOAP clients to no more than the number of web
tasks specified in the WebParams.dat file on the
i.
LON 100. The default for this number
is five.