Stream benchmark methodology

How rpc edge compares SubscribeDeshred with processed Yellowstone gRPC using paired transaction signatures.

The stream lifecycle benchmark races two rpc edge subscription stages using the same account filter and matches observations by transaction signature.

What is compared

• SubscribeDeshred: pre-execution transaction intent decoded from shreds.
• Processed gRPC: post-execution transaction metadata from Yellowstone gRPC.

These are different lifecycle stages, not interchangeable provider endpoints. The report answers how much earlier the pre-execution stage becomes observable for this workload.

Clock and pairing

The benchmark records client monotonic receipt time. For each signature, the first arriving stream receives zero non-negative lag; later streams are measured relative to it. A separate signed value, deshred - processed, preserves direction: negative means deshred arrived first. Provider created_at timestamps may be retained diagnostically, but do not replace client receipt time.

Published run controls

• profile: pump_amm_transactions_v1;
• account: pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA;
• target: 50,000 paired observations;
• actual: 55,424 paired observations;
• host: Cherry Servers Frankfurt, public IP 185.191.118.181;
• duration: 5 minutes 18 seconds;
• errors and disconnects: zero on both streams.

See the reviewed report or raw evidence.