Edit /etc/hxcore/daemon.conf:
[global] policy = dynamic_hybrid sample_rate_us = 100 thermal_emergency = 85
[cpu_map] p_cores = 0-7,16-23 e_cores = 8-15,24-31 accelerators = 32-35
To evaluate HXCORE.OL properly, one must look beyond the headline numbers. As of the most recent quarterly filing (Q4 2025), the company reported the following key metrics:
+--------------------------------------------------------------+
| hxcore.ol (C++ core) |
| +----------------------+ +---------------------------+ |
| | Arena Manager | | Schema Registry | |
| | - mmap, shm, heap | | - compile-time / runtime | |
| +----------+-----------+ +-----------+---------------+ |
| | | |
| +----------v-----------+ +-----------v---------------+ |
| | Object Store | | Accessor Engine | |
| | - Handles ↔ pointers| | - Inline getters/setters | |
| +----------+-----------+ +-----------+---------------+ |
| | | |
| +----------v-----------+ +-----------v---------------+ |
| | Buffer View Layer | | Serialization Backends | |
| | - Python buffer | | - Binary, JSON, Protobuf| |
| +----------------------+ +---------------------------+ |
+--------------------------------------------------------------+
The Python package (hxcore.ol) is a thin C‑extension that forwards calls to the C++ core.
All read‑only operations are lock‑free; writes go through a mutation guard that uses a per‑arena std::atomic_flag to ensure exclusive access. hxcore.ol
Running a multimodal LLM on an edge device (like an NVIDIA Jetson or an Intel Core Ultra) requires juggling CPU, GPU, and NPU. Hxcore.ol automates this split, sending transformer attention mechanisms to the NPU while managing token generation on the CPU. The result? Battery life improvements of up to 50% for the same inference quality.
At its core, hxcore.ol represents a dynamic overlay framework for heterogeneous core processing. The "hx" prefix denotes heterogeneous execution, while "core" refers to both physical CPU cores and logical processing units. The suffix ".ol" stands for overlay library, indicating that this is not a standalone operating system but a middleware layer that sits between the bare metal and the hypervisor or OS kernel. Edit /etc/hxcore/daemon
Unlike traditional core schedulers (such as Linux’s CFS or Windows’ Thread Scheduler), hxcore.ol utilizes real-time workload fingerprinting. It analyzes instruction streams at the microsecond level and dynamically reassigns threads to the most appropriate core type—whether high-performance (P-cores), efficiency (E-cores), or specialized accelerator cores (e.g., GPGPU or NPU blocks).