# FIX/FAST PMAP & Stop-Bit Decoding Latency Bottlenecks

> Analyze why FIX Adapted for STreaming (FAST) Presence Maps (PMAP), 7-bit stop-bit varints, and stateful field operators lose to SBE on 10GbE+ market feeds.

Canonical: https://terminalledgerdesk.com/reports/fix-fast-protocol-pmap-stop-bit-decoding-cpu-latency-bottlenecks
Last updated: 2026-11-14T20:05:32.461Z

**Publication:** Terminal Ledger Desk
**Category:** Fix Protocol Sbe Ouch Session Latency
**Published:** 2026-11-14T12:55:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

Although FIX/FAST compresses market data wire bytes by 75% via Presence Maps and Delta/Copy field operators, serial 7-bit stop-bit scanning and inter-packet state coupling create severe CPU bottlenecks.

## Key takeaways

- Above 2.86 Gbps link speed, SBE fixed-offset decoding beats FAST variable-length stop-bit compression in total wire-plus-CPU latency (161.8 ns vs 297.4 ns at 10GbE).
- Stop-bit varints force sequential byte scanning because field k+1 has no known memory offset until every preceding field stop bit (0x80) is located.
- SIMD _mm_movemask_epi8 combined with x86 BMI2 _pext_u64 accelerates legacy FAST 1.2 integer unpacking by 3.4x (940 ns down to 275 ns).
- Unreset stateful Delta and Copy dictionaries silently fabricate corrupted prices after UDP packet drops unless per-datagram FAST Reset (Template 120) is enforced.

## Related financial entities

- **CME Aurora Financial Data Center Standard** (CME-AURORA) — product: Dedicated CME Group hosting facility in Aurora, Illinois, housing the Globex matching engine and offering direct low-latency colocation to clearing members.
- **Financial Information eXchange (FIX) Protocol** (FIX-4.4) — product: Electronic communications protocol initiated in 1992 for international real-time exchange of securities transaction and market data information.
- **Financial Information eXchange (FIX) Protocol Standard** (FIX-STANDARD) — product: Universal electronic messaging standard that facilitates real-time communication of securities transactions and market data across global financial institutions.

## Analysis

Designed in 2006 when 100 Mbps WAN circuits constrained exchange multicast distribution, **FIX Adapted for STreaming (`FAST 1.1 / 1.2`)** achieved remarkable 70% to 82% wire compression using Presence Maps (`PMAP`), 7-bit stop-bit variable-length integers, and stateful dictionary operators (`Copy`, `Increment`, `Delta`). On modern 10GbE and 100GbE colocation fabrics, however, trading bandwidth savings for serial bit-by-bit CPU decoding proved backwards: decoding a compressed 28-byte FAST tick costs 5.5x more CPU latency than casting a 96-byte stateless SBE frame.

## Serial Dependency Chain of 7-Bit Stop-Bit Variable-Length Integers

In the [FIX/FAST messaging specification](/engines/fix-protocol-messaging-standard), every field—including the leading `PMAP` itself and `TemplateID`—is serialized using **stop-bit encoding**: bits `0..6` of each byte carry data payload while the most significant bit (`Bit 7`, `0x80`) acts as a continuation terminator (`0 = more bytes follow`, `1 = final byte of field`).

Because field `k + 1` begins at whatever dynamic byte index field `k` happened to set its `0x80` stop bit, the CPU faces a **strict sequential data dependency**. To read field 10 (`MDEntryPx`), the decoder MUST scan every byte of fields 1 through 9 first! Unlike [ASCII FIX vs SBE zero-copy structs](/reports/fix-4-4-ascii-tag-value-parsing-vs-sbe-zero-copy-wire-latency) where SBE jumps straight to `buffer + 48` in 1 cycle, FAST stalls out-of-order CPU execution pipelines on unpredictable stop-bit branches.

![FIX/FAST stop-bit 0x80 byte scanning, PMAP bitmask lookup, and stateful Delta/Copy dictionary mutation](/api/figure?type=flow&title=FIX%2FFAST%20Stateful%20Stop-Bit%20Decoding%20Pipeline&subtitle=Why%20variable-width%207-bit%20fields%20create%20sequential%20CPU%20dependencies%20vs%20SBE&steps=1.%20Stop-Bit%20Scan%3A%3AFind%20MSB%200x80%20boundary%20via%20movemask%2Bctz%7C2.%20PMAP%20Bit%20Read%3A%3ATest%20presence%20bit%20per%20template%20operator%7C3.%20PEXT%20Unpack%3A%3AStrip%20bit%207%20via%20BMI2%20_pext_u64%20mask%7C4.%20Dict%20Mutate%3A%3AApply%20Copy%20%2F%20Delta%20%2F%20Increment%20to%20state&metrics=WIRE%20COMPRESSION%3A%3A76.4%25%3A%3A28B%20FAST%20vs%20118B%20ASCII%20FIX%7CNAIVE%20DECODE%20P99%3A%3A940%20ns%3A%3AByte-loop%20stop-bit%20branches%7CBMI2%20PEXT%20P99%3A%3A275%20ns%3A%3ASIMD%20movemask%20%2B%20_pext_u64%7CSBE%20EQUIVALENT%3A%3A85%20ns%3A%3AStateless%20fixed-offset%20cast)

## Stateful Dictionary Operators (`Copy`, `Delta`, `Increment`) and Packet-Loss Fragility

FAST achieves extreme compression by maintaining a mutable **Previous Value Dictionary** shared between encoder and decoder across consecutive messages:

- **`Copy` Operator**: If `SecurityID` or `MDEntrySize` matches the previous message, its `PMAP` bit is `0` and **zero bytes** are sent on the wire; the decoder copies the prior dictionary value.
- **`Delta` Operator**: Always present on the wire; transmits only the signed integer difference (`Price_new - Price_prev`) added to the prior dictionary entry.
- **`Increment` Operator**: When `PMAP` bit is `0`, the decoder auto-increments the prior `MsgSeqNum` or `RPTSeq` by `+1`.

Here lies the fatal multicast flaw: if a single UDP packet drops without an explicit `FAST Reset (Template 120)` boundary at the start of every datagram, applying a `Delta` of `+25 ticks` onto a stale prior dictionary value silently fabricates **phantom prices**! That hazard drove CME, Eurex, and B3 (UMDF Puma -> Binary) toward stateless [CME MDP 3.0 SBE multicast](/reports/cme-mdp-3-0-sbe-incremental-refresh-channel-arbitration-recovery).

| Codec Attribute | FIX/FAST `1.1` / `1.2` | FIX SBE `v8` ([Aurora](/engines/cme-aurora-colocation-standard)) | Nasdaq ITCH `5.0` |
| :--- | :--- | :--- | :--- |
| **Integer Encoding** | 7-bit Stop-Bit VarInt (Big-Endian) | Fixed `int32` / `int64` (Little-Endian) | Fixed `uint32` / `uint64` (Big-Endian) |
| **Field Offset Determinism** | `O(k)` sequential scan of prior `k-1` fields | `O(1)` compile-time constant byte offset | `O(1)` fixed struct offset |
| **Cross-Message State** | Stateful `Copy` / `Delta` / `Increment` dict | 100% Stateless self-contained frame | Stateless (OrderRef slab in book) |
| **10GbE Wire + CPU Total** | ~297 ns (BMI2) / ~962 ns (Scalar) | ~162 ns | ~155 ns |
| **Ideal Network Regime** | Bandwidth-capped WAN / Satellite (`<100 Mbps`) | 10GbE / 25GbE / 100GbE Colocation | 10GbE / 40GbE Colocation |

## Wire Compression vs CPU Decode Tradeoff: FAST 1.2 vs SBE vs ITCH

Comparing legacy international venues still publishing FAST feeds (select emerging-market and fixed-income feeds) against binary SBE and ITCH highlights the modern bandwidth-for-cycles inversion.

```formula
T_total(R_link) = (L_bytes * 8) / R_link + T_cpu_decode
R_crossover = 8 * (L_sbe - L_fast) / (T_cpu_fast - T_cpu_sbe)

Where:
 L_fast = 74 bytes (46B Eth/IP/UDP + 28B FAST payload)
 L_sbe = 142 bytes (46B Eth/IP/UDP + 96B SBE payload)
 T_cpu_fast = 275 ns (optimized BMI2 PEXT decoder); T_cpu_sbe = 85 ns

Worked Bandwidth Crossover Point:
 R_crossover = 8 * (142 - 74) bytes / (275 - 85) ns
 = 544 bits / 190 ns = 2.863 Gbps!
 Conclusion: On any link faster than 2.86 Gbps (all 10G/25G/100G exchange cross-connects), SBE beats FAST.
```

## Accelerating Legacy FAST Decoders With PEXT Bit-Extraction Lookup Tables

Many cross-border prop desks trading APAC, LatAm, or legacy OTC feeds via [FIX API hubs](/software/fix-api) must still ingest FAST 1.1/1.2 streams at ultra-low latency. Rather than looping byte-by-byte (`while (!(b & 0x80))`), low-latency C++ FAST decoders load 16 bytes at once into an XMM register, extract all 16 stop bits into a 16-bit integer mask via `_mm_movemask_epi8(chunk)`, and use `__builtin_ctz(mask)` (Count Trailing Zeros) plus BMI2 `_pext_u64(raw64, 0x7F7F7F7F7F7F7F7FULL)` to strip stop bits and pack 7-bit payload groups in **3 hardware instructions**!

Combining `movemask + ctz + _pext_u64` cuts FAST decode latency from `940 ns` down to `275 ns` per incremental tick—still slower than `85 ns` SBE, but fast enough to prevent RX socket drops during opening auctions. Review our [FIX, SBE & OUCH Session Architecture Guide](/reports/fix-protocol-sbe-ilink3-ouch-session-latency-architecture-guide) for full multi-venue codec rankings.

![Wire serialization time plus CPU decode latency at 100Mbps WAN vs 10GbE colocation for FAST and SBE](/api/figure?type=bars&title=Total%20Wire%20%2B%20CPU%20Latency%3A%20100%20Mbps%20WAN%20vs%2010GbE%20Colocation&subtitle=Demonstrating%20the%2010GbE%20crossover%20where%20SBE%20beats%20FAST%20despite%20larger%20byte%20size&steps=100Mbps%20WAN%20%20FAST%20%2828B%29%3A%3A2%2C240%20ns%20wire%20%2B%20275%20ns%20CPU%20%3D%202%2C515%20ns%7C100Mbps%20WAN%20%20SBE%20%2896B%29%3A%3A7%2C680%20ns%20wire%20%2B%2085%20ns%20CPU%20%3D%207%2C765%20ns%7C10GbE%20Colo%20%20FAST%20%2828B%29%3A%3A22.4%20ns%20wire%20%2B%20275%20ns%20CPU%20%3D%20297.4%20ns%7C10GbE%20Colo%20%20SBE%20%2896B%29%3A%3A76.8%20ns%20wire%20%2B%2085%20ns%20CPU%20%3D%20161.8%20ns&metrics=10GBE%20SBE%20WIN%3A%3A-45.6%25%3A%3A161.8%20ns%20SBE%20vs%20297.4%20ns%20FAST%7C100GBE%20SBE%20WIN%3A%3A-67.9%25%3A%3A92.7%20ns%20SBE%20vs%20288.2%20ns%20FAST%7CSTOP-BIT%20OVERHEAD%3A%3A14.3%25%3A%3A1%20control%20bit%20per%207%20data%20bits%7CCORRUPTION%20RISK%3A%3AZero%20in%20SBE%3A%3ANo%20cross-packet%20Delta%20state)

## Mandatory Per-Datagram Dictionary Reset Verification

When connecting to any remaining FAST multicast venue audited under [FCA](/standards/fca) or [MAS](/standards/mas) algorithmic controls, confirm whether the exchange prepends an implicit or explicit `FAST Dictionary Reset` on every UDP datagram:

- **Per-Packet Reset Enabled**: Each UDP datagram is self-contained; packet N+1 can be buffered and decoded cleanly even if packet N was lost on the WAN.
- **Stream-Scoped Dictionary (No Per-Packet Reset)**: Any single missed sequence number **invalidates all subsequent `Copy` and `Delta` prices** until the next scheduled `Reset` message! Your feed handler MUST immediately mark the order book stale, halt outbound quoting, and recalibrate exposure limits in the [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator). Explore more market-data specs in the [FIX, SBE & OUCH Topic Hub](/topics/fix-protocol-sbe-ouch-session-latency).

## Frequently asked questions

### What is a Presence Map (PMAP) in the FIX/FAST market data protocol?

A Presence Map is a stop-bit-encoded bitmask at the start of a FAST message segment where each bit indicates whether an operator-controlled field (such as Copy, Default, or Increment) is explicitly transmitted on the wire (1) or derived from dictionary state (0).

### Why does a FAST Delta operator not consume a bit inside the message PMAP?

Under the FAST specification, mandatory Delta fields are always transmitted on the wire (even if the delta value is 0, sent as single byte 0x80), so they never require a PMAP bit; optional Delta fields use a nullable representation where 0x80 denotes NULL.

### How does x86 BMI2 _pext_u64 speed up FAST stop-bit integer decoding?

Instead of shifting and masking 7 bits at a time in a loop with data-dependent branches, _pext_u64 extracts all non-stop payload bits across up to 8 bytes simultaneously using mask 0x7F7F7F7F7F7F7F7F in 3 CPU cycles on modern Intel and AMD cores.

### Do any institutional venues still use FIX/FAST in 2026?

While CME, Eurex, Nasdaq, NYSE, Cboe, LSEG, and B3 migrated primary colocation feeds to binary SBE, ITCH, or Pillar protocols, several regional stock exchanges, fixed-income ECNs, and bandwidth-throttled WAN distributor feeds still publish FAST 1.1/1.2 streams.


## Source URLs

- https://www.fixtrading.org/standards/fast/
- https://www.fixtrading.org/standards/sbe-online/
- https://www.cmegroup.com/confluence/display/EPICSANDBOX/MDP+3.0+-+Market+Data+Incremental+Refresh

## Citation

- APA: Marcus Thorne, CQF. (2026). FIX/FAST Protocol PMAP & Stop-Bit Decoding: Why Exchanges Migrated to SBE. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/fix-fast-protocol-pmap-stop-bit-decoding-cpu-latency-bottlenecks
- Canonical article: [FIX/FAST Protocol PMAP & Stop-Bit Decoding: Why Exchanges Migrated to SBE](https://terminalledgerdesk.com/reports/fix-fast-protocol-pmap-stop-bit-decoding-cpu-latency-bottlenecks)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
