|Platform||Supported OS||Supported architecture|
|Android||Android 6+||x86, arm64-v8a or armeabi-v7a ABI|
|Linux||Ubuntu 18.04+ or Alpine 3.9+||x86_64, aarch64, armv7 or arm|
|Docker||Docker 20+||x86_64 or aarch64|
|macOS||Big Sur||x86_64 or aarch64 (via Rosetta emulation)|
It is not supported to put firewalls between devices of the same swarm. Wherever possible, devices should be placed within one broadcast domain. Placing devices of the same swarm across different broadcast domains requires setting up a bootstrap node and configuring communication between these broadcast domains accordingly.
A lot of different factors play into performance of Actyx and your apps. Assuming a standard network setup, rugged tablets or other devices with relatively low computing power, and a standard factory use case, these are approximate limits:
|Latency||below 200 ms, not guaranteed as dependent on several factors|
|No. of nodes||max. 100 nodes|
|Event data rate||~1 event per node per 10 seconds|
The following list shows the factors that influence performance. Please note that these are not requirements, but assumptions made for the above performance characteristics:
|LAN setup and latency||standard / WiFi|
|App runtimes||Webview (Node.js) and Docker|
|Devices||Rugged tablets or other devices with relatively low computing power (e.g. Raspberry Pi 3)|
|Device CPU||1-2 GHz, x86/arm architecture|
|Device RAM||1-4 GB|
|Business logic complexity||Standard factory use case, production data and machine data acquisition|
Assumptions do not fit your use case?
The limits regarding performance and disk space described on this page are only true within the circumstances outlined above. If one of these factors changes, the limits for your solution might change. If you are looking for guidance on a specific use case, please refer to our conceptual guide or contact us.
The required disk space depends on the size, number, and compressibility of the events that are emitted by apps built on Actyx. These are example calculations for factory apps, either with or without machine integrations, based on our project experience and for a 1-year time frame:
|With machine integrations||Without machine integrations|
|Number of nodes||8||10|
|Number of events||10,000,000||580,000|
|Disk space needed||135 MB||36 MB|
The events used for the above examples contained information on orders and their progress, or machine values (~10) read from a OPC UA interface.
We are already working on the functionality to configure replication and lifespan of events. By configuring when events should be deleted or to which devices they should be replicated, you will be able to optimize for low disk space usage.
Which settings are available and which values they may have is defined in the so-called ActyxOS Node Setting Schema. The most recent version thereof is available for download at: