This document explains the performance your Miniserver can provide.
The Loxone Miniserver offers more than enough power for each family home and some reserves. Learn more and use the resources of your Miniservers.
PERFORMANCE OF MINISERVER
The Miniserver was conceived for a single-family house, but it also offers some services. Up to 30 extensions can be connected to a Miniserver.
The online status of extensions is queried via the LoxBus every 10 min.
The Miniserver has a 400 MHz strong processor and has 64MB of RAM. Approximately 10 MB is used for the operating system. The free memory is used for processing the program and for all communication tasks (with apps, browsers, etc.).
For more info please see the Miniserver Capabilities Documentation.
EXAMPLES OF MEMORY REQUIREMENTS
In order to estimate whether the memory consumption of your Miniservers is adequate, we have recorded examples from our installations for you.
MINISERVER WITHOUT ENLARGEMENT AND PROGRAM CONTENTS
- Components: 1 x Miniserver
- Memory consumption: 6.490kB / 56.241kB (11.5%)
- Processes: 35 tasks
- File size: up to 100 kB
MINISERVER FOR THE GATEWAY:
- Components: 1 x Miniserver
- Memory consumption: 5.984kB / 56.241kB (10.6%)
- Processes: 37 Tasks
- File size: 83 kB
MINISTER WITH ENLARGEMENT FOR CONTROLLING A APARTMENT
- Components: 1 x Miniserver, 1 x expansion, 7 virtual inputs, 4 virtual outputs
- Memory consumption: 11.591kB / 56.241 kB (20.6%)
- Processes: 40 tasks
- File size: 169 kB
MINISERVER WITH ENLARGEMENT AND EIB CONNECTION FOR CONTROLLING A FAMILY HOME
- Components: 1 x miniserver, 13 x extension, 214 EIB sensors, 91 virtual inputs, 69 virtual outputs
- Memory consumption: 15.521kB / 56.241kB (27.6%)
- Processes: 51 Tasks
- File size: 1,500 kB
TIP FOR OPTIMIZING MEMORY CONSUMPTION
Your Miniserver has an unusually high memory consumption? Through a well thought-out configuration the memory consumption can usually be optimized. Read what should be observed during configuration:
STORAGE OF ANALOG VALUES IN STATISTICS AND LOGS
The Miniserver works as a standard with a cycle time of 50 Hz, ie the entire program is processed 50 times per second (the minimum cycle time of the miniserver is 200 Hz).
If you record sensor values from analog inputs in the statistics or in log files, please make sure you have a meaningful polling cycle. The polling cycle “each change” means that sensor values are written to the statistics 50 times per second as a standard! In sum, this results in 50 write accesses to the SD card per second.
So, when recording analog values, use a mean value to relieve memory and CPU of the miniserver. In addition, much less memory is consumed on the SD card.
SAVE MEMORY RESERVE
To ensure that the Miniserver does not fall into a trap, at least 10 MB should always be available for running (dynamic tasks such as web requests, …).
ERROR BY EARLY SAVING
In order to prevent the Miniserver from entering a deadlock (two blocking processes) due to a lack of memory, the file should be stored in a Miniserver at an early stage so that the memory consumption can be checked.
If your Miniserver is reachable externally, it is recommended to use a port other than the standard port 80. For more details, see online sharing .
In addition, the Miniserver has a firewall for protection. It recognize attack scenarios independently and blocks the attacking IP addresses.
NO IMPROVEMENT? CONTACT US!
You have followed our advice, but the memory consumption of your Miniserver is nevertheless unusually high? Please contact us and we will get to the bottom of the problem.