First-detection share
The percentage of matched transactions where a provider delivered the first valid update. This is the headline metric for latency-sensitive systems because it shows who sees the same transaction first most often.
// Geyser gRPC benchmark
A head-to-head benchmark comparing Shreder Fastlane and Helius LaserStream for Solana Geyser gRPC delivery in Frankfurt.
In this 10,000-transaction Frankfurt run, Shreder Fastlane delivered 86.37% of matched transactions first, compared with 13.63% for Helius LaserStream. The published latency deltas for Helius were p50 2.92 ms, p95 26.58 ms, and p99 45.08 ms in this benchmark.
// Published run
| Benchmark | Shreder Fastlane vs Helius LaserStream |
|---|---|
| Product class | Yellowstone-compatible Solana Geyser gRPC |
| Shreder endpoint | Shreder Fastlane Frankfurt |
| Comparison endpoint | Helius Frankfurt / Helius LaserStream |
| Test location | Frankfurt, Teraswitch FRA2 |
| Sample size | 10,000 transactions |
| RTT min / avg / max / mdev | 0.066 / 0.102 / 0.221 / 0.042 ms |
| Benchmark tool | GeyserBench |
| Subscription filter | High-activity transaction filter (pump.fun) |
| Commitment level | processed (typical for low-latency Geyser benchmarks) |
Derived stat: Shreder Fastlane delivered the first update about 6.3× more often than Helius LaserStream in this published run (86.37 ÷ 13.63). This is a ratio for this run only, not a universal performance multiplier.
// First detection and latency
| Provider | First-detection share | p50 latency delta | p95 latency delta | p99 latency delta |
|---|---|---|---|---|
| Shreder Fastlane Frankfurt | 86.37% | 0.00 ms | 0.00 ms | 0.00 ms |
| Helius LaserStream Frankfurt | 13.63% | 2.92 ms | 26.58 ms | 45.08 ms |
First-detection share shows which provider delivered the same matched transaction first. Latency percentiles summarize the reported delivery-time delta distribution for this benchmark. p50 is the median case, while p95 and p99 show tail behavior.
Shreder 0.00 ms row doesn't mean literal zero network latency. It is the published latency-delta result in this benchmark table. End-to-end latency always includes network transport, stream processing, and downstream application logic.
// Interpretation
This benchmark is a race between two Solana Geyser-class data streams. For each matched transaction observed by both endpoints, the benchmark records which provider delivered the first valid update to the benchmark client.
In this run, Shreder Fastlane delivered the first update for most matched transactions. Helius LaserStream still delivered some transactions first, which is why the result should be read as a distribution.
The metrics in this report are defined as follows.
The percentage of matched transactions where a provider delivered the first valid update. This is the headline metric for latency-sensitive systems because it shows who sees the same transaction first most often.
The median observed delivery-time delta in the benchmark. This shows the typical difference for matched events in the run.
The 95th percentile delivery-time delta. Useful for understanding tail behavior beyond the median.
The 99th percentile delivery-time delta. Matters for trading, searchers, alerting, and systems where rare slow updates can still be costly.
The number of matched transactions included in the comparison. Larger samples are less vulnerable to random variance.
Round-trip time from the benchmark environment to the endpoint or measured network path. Lower RTT can improve delivery speed, so region and network placement should be disclosed.
Takeaway: in this Frankfurt benchmark, Shreder Fastlane won first delivery for 86.37% of matched transactions while preserving a Yellowstone-compatible Geyser gRPC interface.
// Comparison context
Helius positions LaserStream as a reliable, low-latency, fault-tolerant alternative to Yellowstone gRPC for streaming Solana blocks, accounts, and transactions—with emphasis on compatible migration, high throughput, and low-latency delivery.
Shreder Fastlane sits in the same Yellowstone-compatible Geyser gRPC category. This benchmark compares two low-latency streams in Frankfurt; it is most relevant for teams already using, or evaluating, a Geyser-class provider for production workloads.
Fastlane changes the delivery implementation, not the client model. Existing Yellowstone-compatible clients keep the same subscription patterns and stream handling—you update the endpoint and token while Shreder’s accelerated path reduces time-to-data.
Fastlane targets up to 2× lower latency through Shreder’s custom implementation while preserving data consistency and accuracy.
Use the same Yellowstone-compatible stream model, clients, filters, and update handling.
Fastlane uses Shreder’s custom implementation to reduce delivery time while keeping the interface stable.
Shreder guarantees data consistency and accuracy while optimizing for the fastest possible Geyser-compatible delivery.
// Correctness
Fastlane is built for low latency, but the stream still needs to be accurate, consistent, and usable by production systems. Shreder guarantees data consistency and accuracy while delivering the fastest Shreder Geyser-compatible path.
When benchmarking a provider, validate more than arrival time. Check transaction signatures, slots, account keys, update counts, commitment transitions, and reconnects.
// Who this matters for
A few milliseconds can matter more in some Solana workloads than others. Use this benchmark as a signal when first visibility affects downstream decisions.
Earlier transaction and account updates can improve reaction time for quoting, hedging, routing, and risk checks.
First-detection share matters when the system needs to observe relevant on-chain events before competitors.
Pools, vaults, and feeds can be streamed through Yellowstone-compatible filters when freshness matters.
Faster account and transaction updates improve how quickly users see activity, confirmations, and balance changes.
It measures which provider delivered the same matched Solana transaction first to the benchmark client. The page reports first-detection share and p50, p95, and p99 latency deltas for Shreder Fastlane Frankfurt and Helius LaserStream Frankfurt in a 10,000-transaction run.
In the published Frankfurt run, Shreder Fastlane delivered 86.37% of matched transactions first, while Helius LaserStream delivered 13.63% first. The published Helius latency deltas were p50 2.92 ms, p95 26.58 ms, and p99 45.08 ms.
The Shreder row shows the published latency-delta output for this benchmark table. Do not interpret it as literal zero network latency. Every real stream has transport, processing, decoding, and application latency. The table is reporting relative delivery-time deltas for the benchmark.
First-detection share is the percentage of matched transactions where a provider delivered the first valid update among the tested providers. For latency-sensitive systems, it is often more useful than a simple average because it shows who wins the data-delivery race most often.
Both products are relevant to teams evaluating low-latency Solana streaming through a Geyser-class or Yellowstone-compatible interface. Helius positions LaserStream as a low-latency, reliable Solana streaming product, while Shreder Fastlane is Shreder's accelerated Yellowstone-compatible Geyser gRPC mode.
Yes. Fastlane is designed to be 100% compatible with Yellowstone gRPC. Existing Yellowstone-compatible clients can keep the same general subscription model, protobuf update handling, and stream logic while changing the endpoint and token to Shreder.
Compatibility describes the interface. Speed depends on the delivery implementation. Fastlane keeps the Yellowstone-compatible interface but uses Shreder's custom accelerated implementation to reduce time-to-data.
You can run a similar benchmark using a GeyserBench-style setup: configure Shreder Fastlane and the comparison endpoint, use the same account or transaction filter, run both endpoints from the same machine, and compare first-detection share plus p50, p95, and p99 latency deltas. Exact public reproducibility depends on whether the monitored account, endpoint configuration, tool version, and run context are published.
Use Regular Geyser when you want reliable Yellowstone-compatible delivery and cost efficiency. Use Fastlane when your workload is latency-sensitive and you want Shreder's fastest Geyser-compatible stream.
Use Fastlane when you need Yellowstone-compatible Geyser data such as accounts, slots, blocks, transaction statuses, and standard Geyser semantics. Use Binary when your workload is focused on compact serialized transaction bytes extracted from shreds.
Yes. Share your current provider, region, filters, commitment level, and target workload. Shreder can help you run a side-by-side benchmark against Fastlane in the region closest to your production systems.
// Test your own workload
The published Frankfurt run shows Fastlane ahead of Helius LaserStream for most matched transactions. The next step is to test your own filters, region, and production workload.