> So the plugin is split across the ESP32's two cores. The control loop and its sensor event handlers own core 0. The exporter gets its own FreeRTOS task pinned to core 1, where a blocking TLS handshake can never touch extraction:
I spent several years working on the technical side of HFT trading operations and this is also an issue with exchange gateways.
e.g. you want both to be true:
- fastest possible path through the gateway
- the ability to log EXACTLY when messages flowed through
The way this was accomplished was to split each direction (e.g. in and out) to a single core and then have an additional core for logging.
> So the plugin is split across the ESP32's two cores. The control loop and its sensor event handlers own core 0. The exporter gets its own FreeRTOS task pinned to core 1, where a blocking TLS handshake can never touch extraction:
I spent several years working on the technical side of HFT trading operations and this is also an issue with exchange gateways.
e.g. you want both to be true:
- fastest possible path through the gateway
- the ability to log EXACTLY when messages flowed through
The way this was accomplished was to split each direction (e.g. in and out) to a single core and then have an additional core for logging.
Feels like AI slop writing
It is. I read the first sentence and closed the tab.