High-Performance Computing for KNX Data Analytics: Xeon 28 Core 2.2GHz in EcoStruxure Building Operation
SpaceLogic KNX Forum
Schneider Electric SpaceLogic KNX forum to get support and share knowledge including selection, installation and troubleshooting for spaceLYnk, Wiser for KNX, eConfigure KNX, SpaceLogic KNX Hybrid module and other topics.
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
2025-10-2208:07 AM
High-Performance Computing for KNX Data Analytics: Xeon 28 Core 2.2GHz in EcoStruxure Building Operation
Hello KNX Community,
We are designing a centralized management system for a large-scale building automation project utilizing a extensive KNX installation. Our goal is to use EcoStruxure Building Operation to not only control the system but also to perform long-term, data-intensive analytics on energy consumption, occupancy patterns, and predictive maintenance.
I would like to understand the community's perspective on the following:
Data Processing & Historical Logging: For those running large KNX installations with years of historical data, has anyone evaluated the need for such a high core-count processor? Is the primary bottleneck for large-scale analytics typically the EIB/KNX TP bus itself, the database I/O, or the computational power needed for processing the data?
Virtualization & Consolidation: We plan to host the Building Operation server, a dedicated historian database (like a SQL server), and potentially other building management services on a single physical host using virtualization. Would a Xeon with 28 cores provide significant headroom for consolidating these KNX-related workloads, or is it overkill for the primarily I/O-bound nature of KNX data acquisition?
EcoStruxure Integration: From a best practices standpoint, are there known benefits or potential compatibility considerations when pairing the EcoStruxure Building Operation platform with such a high-parallelism CPU architecture? Does the software efficiently leverage multiple cores for its internal processes and analytics engines?
Future-Proofing for KNX IP & Secure Connections: As KNX IP and cloud connectivity become more prevalent, having headroom for encryption, data translation, and secure session handling is crucial. Could the high core count of this Xeon be beneficial for offloading these tasks without impacting core control logic performance?
Any insights from your experiences with large deployments, performance benchmarking, or server sizing for data-heavy KNX projects would be greatly appreciated.