perf(worker): event hot-path allocation + flush cuts (WRK-06/11/12, IPC-15)
WRK-06: MxStatusProxyConverter caches the four resolved FieldInfo per status type in a static ConcurrentDictionary (the GetField metadata scan ran 4x per status per event on the STA path). GetValue+Convert.ToInt32 still run per event (late-bound RCW). Exceptions byte-identical: missing-field message unchanged (ResolveField, not cached on throw via GetOrAdd); null-value message unchanged. WRK-11: MxAccessEventQueue.Enqueue takes ownership of the passed MxEvent - stamps WorkerSequence/WorkerTimestamp on it in place and enqueues it, no Clone(). Audited all 3 callers (base/alarm event sinks, provider-mode handler): each builds a fresh event per Enqueue, none reuse it. MxAccessValueCache.Set now deep-copies its retained Value/SourceTimestamp/Statuses so the cache snapshot never aliases the queue-owned (later serialized) event. Net: alarm/other events clone nothing (was full clone); data-change clones payload-only. WRK-12: WorkerFrameWriter coalesces the flush across a drained batch - each frame is written but not flushed individually; one FlushAsync after the batch, then all written frames complete. Preserves the written+flushed completion contract; a burst of N events costs 1 flush, not N. On write failure the whole in-flight batch + queue fail so no caller hangs. IPC-15 (doc): the multi-event WorkerEnvelope body remains unimplemented (wire still carries one event per worker_event frame); gateway.md Performance section now distinguishes the shipped flush-coalescing from that deferred proto change. net48-safe (no init/records; readonly struct cache entry). Worker builds x86 only - verification on windev. Tests added: converter cache-reuse, queue ownership-transfer, value-cache snapshot independence, writer batch-flush-once. Claude-Session: https://claude.ai/code/session_01DMXXvNuPekkkrTEyPNxEkW
This commit is contained in:
+6
-1
@@ -884,7 +884,12 @@ Baseline choices:
|
||||
Optimizations after parity:
|
||||
|
||||
- batch commands where MXAccess semantics allow,
|
||||
- batch events from worker to gateway while preserving order,
|
||||
- batch events from worker to gateway while preserving order. Implemented so
|
||||
far: the worker frame writer coalesces the *flush* across a drained batch of
|
||||
event frames, so a burst costs one flush syscall rather than one per event
|
||||
(WRK-12). Still not implemented: a multi-event `WorkerEnvelope` body that
|
||||
packs several events into a single frame — the wire still carries one event
|
||||
per `worker_event` frame (IPC-15), so this remains an additive-proto change,
|
||||
- optional data-change coalescing by item handle,
|
||||
- memory-mapped payload slabs for very large arrays,
|
||||
- shared schema for typed values to avoid raw COM marshaling at the gateway,
|
||||
|
||||
Reference in New Issue
Block a user