fixtureqa 0.9.0__tar.gz → 0.9.1__tar.gz

{fixtureqa-0.9.0/fixtureqa.egg-info → fixtureqa-0.9.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fixtureqa
-Version: 0.9.0
+Version: 0.9.1
 Summary: FIXture — FIX Protocol Testing Tool
 Requires-Python: >=3.10
 License-File: LICENSE

{fixtureqa-0.9.0 → fixtureqa-0.9.1}/fixture/api/routers/perf.py

@@ -53,6 +53,18 @@ _TERMINAL = ("completed", "stopped", "error")
 # up front (before the run starts) rather than wedging the server.
 DURABLE_SAFE_MSG_RATE = 30  # messages/second a logged/durable session can sustain
 
+# Session configs that add work to the per-message hot path on the event loop —
+# they distort (or, for check_latency, can outright reject messages and corrupt)
+# the very latency a perf run measures. Unlike durable persistence there is no
+# rate at which they're safe, so a run that drives a session with any of them on
+# is refused up front. (label, why) — the Performance-session toggle in the
+# session modal clears all of them.
+_PERF_HOSTILE_KEYS: tuple[tuple[str, str], ...] = (
+    ("validate_inbound", "validates every inbound message against the spec on the loop"),
+    ("check_latency", "parses SendingTime(52) and may reject messages on the loop"),
+    ("enable_last_msg_seq_num_processed", "stamps LastMsgSeqNumProcessed(369) on every outbound message"),
+)
+
 
 def _order_rate_per_s(body: RunConfig) -> float:
     r = body.rate
@@ -144,6 +156,25 @@ async def create_run(body: RunConfig, sm: SM, reg: REG, ts: TS, admin: Admin):
             f"~{safe_order_rate:.0f} orders/s (~{DURABLE_SAFE_MSG_RATE} msg/s) — at "
             f"higher rates the event loop stalls on per-message fsync/DB writes")
 
+    # Per-message latency guard — BEFORE reg.create(). Refuse outright if any
+    # driven session has a perf-hostile key on: these add work to the per-message
+    # hot path on the event loop (or reject messages outright) and distort the
+    # latency the run exists to measure. No safe rate, so unlike the durability
+    # guard this is a hard refusal rather than a throttle.
+    offenders = [
+        (label, attr, why)
+        for label, cfg in participating
+        for attr, why in _PERF_HOSTILE_KEYS
+        if getattr(cfg, attr, False)
+    ]
+    if offenders:
+        detail = "; ".join(f"{label} session has {attr} on ({why})"
+                           for label, attr, why in offenders)
+        raise HTTPException(status_code=409, detail=(
+            f"Refusing to start: {detail}. These add per-message work on the event "
+            f"loop and distort latency measurement — turn them off (or tick "
+            f"'Performance session' in the session modal) before running a perf test."))
+
     # CompIDs from the driving (client, else venue) session — for template tokens.
     drive_sid = body.client_session_id if need_client else body.venue_session_id
     dcfg = sm.get_state(drive_sid).config