CPU Specification per infrastructure
The entire Sewio RTLS system is managed by the RTLS Studio SW. The RTLS Studio also provides interface (data) for other systems that can cooperate together with the Sewio RTLS system and create applications based on the provided data.
Adequate server performance is needed to ensure that the RTLS works properly.
The minimum required computing power depends on the number of tags and their refresh intervals, but also on the number of anchors.
Therefore you need to choose a server configuration that will assure necessary computing power. If the server cannot handle the amount of calculations, it could lead to irrelevant data.
Usually, RTLS Servers are virtualized (on very powerful servers) or provided by local vendors. For the RTLS system, it is very important to have on the server a CPU that is powerful enough to handle position calculation. It is important to have a strong single thread rating but also enough threads because RTLS Studio is a multicore application.
Here is a table with installation size and recommended CPU model and its rating from benchmark tests.
Anchor Deployment | Number of positions per 5min (best estimate) | CPU (Cores/Threads) | CPU Single Thread Rating | CPU Examples | |
|---|---|---|---|---|---|
10 Anchors | 3 Masters | 5000 positions | (4/4) | 2,000 | ~ Intel Xeon E3-1225 v6 @ 3.30GHz |
50 Anchors | 15 Masters | 10,000 positions | (6/12) | 2,000 | ~ Intel Xeon E5-2643 v3 @ 3.40GHz |
| 25,000 positions | (6/12) | 2,500 | ~ Intel Xeon E-2146G @ 3.50GHz | ||
100 Anchors | 30 Masters | 10,000 positions | (6/12) | 2,000 | |
| 25,000 positions | (8/16) | 2,000 | |||
200 Anchors | 60 Masters | 10,000 positions | (8/16) | 2,400 | |
| 25,000 positions | 12/24 | 2,800 | ~ Intel Xeon Silver 4510 | ||
- It is recommended to use https://www.cpubenchmark.net/ for comparison, to check the performance of each CPU.
- If you're searching for CPU recommendation for a large RTLS deployment (e.g. 400 Anchors / 90 Masters), contact Support Team via Sewio Service Desk
- Included in the CPU estimation is the fact that signal from a single Tag can reach up to 30 anchors, Trackables zones are enabled (50 - 200 zones) and possible API integration via WebSocket