Fastlane won the matched race
In this sample, every matched transaction reached the benchmark client through Shreder Fastlane first.
// Geyser gRPC benchmark
A head-to-head benchmark comparing Shreder Fastlane and Alchemy Geyser gRPC for Solana Geyser gRPC delivery in Frankfurt.
In this 10,000-transaction run, Shreder Fastlane delivered the first valid update for 100.0% of matched transactions. Alchemy Frankfurt delivered 0.0% first in this sample, with published latency deltas of p50 19.55 ms, p95 67.17 ms, and p99 102.82 ms.
// Published run
This report summarizes the Alchemy Geyser gRPC run published on the benchmarks hub. Both endpoints were compared with the same monitored workload and the same Frankfurt benchmark environment.
| Benchmark | Shreder Fastlane vs Alchemy Geyser gRPC |
|---|---|
| Product class | Yellowstone-compatible Solana Geyser gRPC |
| Shreder endpoint | Shreder Fastlane Frankfurt |
| Comparison endpoint | Alchemy Frankfurt |
| Test location | Frankfurt, Teraswitch FRA2 |
| Sample size | 10,000 transactions |
| RTT min / avg / max / mdev | 1.312 / 1.317 / 1.329 / 0.006 ms |
| Benchmark tool | GeyserBench |
// First delivery
First-detection share answers a direct question: among matched transactions observed by both endpoints, which provider delivered the first valid update to the benchmark client?
| Provider | First-detection share | p50 latency delta | p95 latency delta | p99 latency delta |
|---|---|---|---|---|
| Shreder Fastlane Frankfurt | 100.0% | 0.00 ms | 0.00 ms | 0.00 ms |
| Alchemy Frankfurt | 0.0% | 19.55 ms | 67.17 ms | 102.82 ms |
The 0.00 ms Shreder row is a latency-delta baseline in this comparison table, not literal zero network latency. End-to-end latency still includes transport, stream processing, client receive time, and application handling.
// Reading the result
This benchmark is not a generic provider ranking. It is one controlled Frankfurt run that shows how the tested Alchemy Geyser gRPC endpoint and Shreder Fastlane behaved under the same benchmark workload.
In this sample, every matched transaction reached the benchmark client through Shreder Fastlane first.
Alchemy’s p95 and p99 latency deltas were materially higher in this run, which matters for workloads sensitive to delayed updates.
Region, filters, commitment level, endpoint plan, client machine, and timestamping method can change benchmark outcomes.
// Provider comparison
Both endpoints belong in the Solana Geyser streaming category. The practical comparison is whether your current stream delivers the data you care about early enough for your application.
| Category | Alchemy Geyser gRPC | Shreder Fastlane |
|---|---|---|
| Interface | Yellowstone-compatible Geyser gRPC | Yellowstone-compatible Geyser gRPC |
| Migration work | Endpoint and token configuration | Endpoint and token configuration |
| Benchmark result | 0.0% first-detection share in this run | 100.0% first-detection share in this run |
| Latency deltas | p50 19.55 ms · p95 67.17 ms · p99 102.82 ms | Baseline row in this run |
// Run your own test
Use the published run as a starting point, then test from your own infrastructure. Keep the comparison fair by matching environment, stream configuration, and measurement rules.
Run both endpoints from the same machine and region, and use the same benchmark window.
Use the same commitment level, account or transaction filters, and timestamping method.
Compare first-detection share, p50, p95, p99 deltas, missed updates, duplicate updates, reconnects, stream errors, and correctness.
It compares which endpoint 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 Alchemy Frankfurt in a 10,000-transaction run.
In this published Frankfurt run, Shreder Fastlane delivered 100.0% of matched transactions first, while Alchemy Frankfurt delivered 0.0% first. The published Alchemy latency deltas were p50 19.55 ms, p95 67.17 ms, and p99 102.82 ms.
No. First-detection share measures who arrived first among matched transactions observed by both endpoints. A 0.0% first-detection share means Alchemy did not deliver the first valid update for any matched transaction in this sample.
Yes. Fastlane keeps a Yellowstone-compatible Geyser gRPC interface. Teams using compatible clients generally keep the same client model and change endpoint and token during migration or testing.
Shreder Fastlane can be used by teams evaluating alternatives to Alchemy Geyser gRPC when they need Yellowstone-compatible Solana streaming with lower latency. The best way to compare both providers is to benchmark them from the same machine, region, commitment level, and filters.
Run both endpoints from the same machine, region, commitment level, filters, measurement window, and timestamping method. Compare first-detection share, p50, p95, p99 latency deltas, missed updates, duplicate updates, reconnects, and stream errors.
No. Treat it as one published Frankfurt run. Production decisions should be based on benchmarks from your region, filters, hardware, commitment level, and application path.
// Test your own endpoint
Use this Alchemy run as a reference point, then test your own filters, machine, region, and production workload.