cortex.core.sync_subscriber¶
sync_subscriber ¶
Thread-backed synchronous subscriber for low-latency control topics.
The async subscriber goes through zmq.asyncio and the asyncio event
loop — that costs ~4 await boundaries per message and limits p99 to
roughly 1 ms even on inproc/IPC. For control loops at >100 Hz where
jitter matters, this implementation runs a dedicated OS thread that
pulls frames synchronously through a zmq.Poller and dispatches to a
sync user callback inline.
On a free-threaded build of CPython (python3.14t, PEP 779) the
receive thread does not contend with the asyncio thread for the GIL,
which is what makes the <100 µs p99 target reachable. The class works
on stock CPython too — just with a higher floor — and emits a one-line
runtime hint when it detects a GIL-enabled interpreter so users know
the upgrade exists.
Public API mirrors :class:cortex.core.subscriber.Subscriber where it
makes sense (topic name, message type, callback, queue size, discovery
plumbing) but diverges in two important ways:
- The callback must be synchronous. Awaiting on a worker thread
would re-introduce the per-await scheduling cost we're trying to
escape. A clear :class:
TypeErroris raised at construction time if a coroutine function is passed. - By default
queue_size=1. For control commands you want the latest message, never a queued backlog. Note that ZMQ'sCONFLATEsocket option cannot be used here — it strips multipart messages, and Cortex publishers always send multipart frames.RCVHWM=1gives the equivalent "drop old, keep newest" effect on the receiver while preserving the wire format.
Attributes¶
SyncMessageCallback
module-attribute
¶
A blocking callback invoked on the receive thread — must not return a coroutine.
Classes¶
ThreadedSubscriber ¶
Bases: SubscriberBase
Synchronous SUB-side receive loop running on a dedicated OS thread.
Lifecycle:
- Construction blocks on a discovery lookup (with optional wait), opens
a fresh sync
zmq.Context, and connects the SUB socket. Construction does not start the worker thread. - :meth:
startspins up the thread; the thread blocks inpoller.poll(timeout_ms)between messages so shutdown is prompt. - :meth:
stopsignals the thread and joins it (with a 1 s default grace period); :meth:closecalls :meth:stopand tears down zmq.
The class is reentrant-safe in the trivial sense that start /
stop / close are idempotent. zmq.SUB itself is single-
threaded; do not call :meth:receive from another thread while the
worker is running.
Source code in src/cortex/core/sync_subscriber.py
60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 | |
Functions¶
start ¶
Spin up the receive thread (idempotent).
Source code in src/cortex/core/sync_subscriber.py
stop ¶
Signal the worker and join it (idempotent).
Source code in src/cortex/core/sync_subscriber.py
close ¶
Stop the worker and tear down zmq state (idempotent).