> For the complete documentation index, see [llms.txt](https://elite-node.gitbook.io/elite-node-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elite-node.gitbook.io/elite-node-docs/technical-deep-dive/understanding-latency-rpc-vs.-grpc-vs.-shredstreame.md).

# Understanding Latency: RPC vs. gRPC vs. Shredstreame

<figure><img src="/files/EVftAhuMEWPjzwrftaql" alt=""><figcaption></figcaption></figure>

* **Standard JSON-RPC (HTTP): \~400-1000+ ms**
  * **Mechanism:** Request-response over TCP/TLS. High overhead per request.
  * **Data:** Finalized or Confirmed blocks only.
  * **Use Case:** General dApp interaction. **Unsuitable for MEV.**
* **Geyser (gRPC): \~50-200 ms (Public Nodes) / < 50-200 ms (Co-located)**
  * **Mechanism:** Persistent, bidirectional streaming over gRPC. Low overhead.
  * **Data:** Processed, fully-formed blocks (post-facto).
  * **Use Case:** High-performance analytics, notifications, **back-running**.
* **Jito Shredstream (gRPC): \~30-50 ms (via Public Relayers) / < 10-30 ms (Co-located)**

  * **Mechanism:** Persistent, bidirectional streaming of raw block fragments.
  * **Data:** Pre-finalization shreds, as they are created by the leader.
  * **Use Case:** The absolute bleeding edge. **Required for competitive front-running.**

**Why This Matters:** The difference between Geyser and Shredstream is the difference between reacting to the past and acting on the present. For strategies aiming to front-run, access to pre-finalization data is the only way to gain the necessary temporal edge.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://elite-node.gitbook.io/elite-node-docs/technical-deep-dive/understanding-latency-rpc-vs.-grpc-vs.-shredstreame.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.