# Stellar Benchmarks

### RPC Method Tested

`getLatestLedger`

### Flood Command

`echo "POST {endpoint}" | vegeta attack -body=payload.json -header="Content-Type: application/json" -rate={100,500} -duration=60s | tee results.bin | vegeta report`

### **Benchmark Summary**

The `getLatestLedger` RPC method tested on Stellar nodes provided by Nodies demonstrates excellent performance across varying load levels. At moderate traffic rates (100–1,000 rps), P99 latency remains under 30ms, ensuring quick and reliable responses. At higher loads (2,500 rps), P99 latency increases to 60ms, which is still very efficient for handling demanding blockchain workloads, with P50 and P90 latencies remaining consistent.

Even under extreme load (5,000 rps), Nodies’ Stellar nodes maintain stable P50 and P90 latencies, with P99 latency rising modestly to 66ms. These results confirm the robustness of Nodies’ infrastructure for Stellar, showcasing the ability to efficiently handle high traffic while maintaining strong performance.

### Latency Benchmarks

**Metrics**: Percentile latencies (in ms), against load rates (100, 1000, 2500, and 5000 rps).

| Rate (rps) | P50 Latency | P90 Latency | P99 Latency |
| ---------- | ----------- | ----------- | ----------- |
| 100        | 17.251      | 20.181      | 25.962      |
| 1,000      | 18.591      | 22.982      | 27.840      |
| 2,500      | 20.782      | 21.128      | 60.201      |
| 5,000      | 20.952      | 30.568      | 65.992      |


---

# Agent Instructions: 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:

```
GET https://docs.nodies.app/performance-benchmarks/stellar-benchmarks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.