Skip to content

Commit 5f2bd4a

Browse files
docs: clarify that results were taken on android
Clarified benchmark results and updated context for testing conditions.
1 parent bf40482 commit 5f2bd4a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs-website/docs/benchmarks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar_position: 8
66

77
# Benchmarks
88

9-
These results are **without prefetch**. A common misconception is that nitro-fetch is only faster when you prefetch it isn't. Plain `fetch` is faster on its own; in our testing around **15–25% faster** than React Native's built-in `fetch` for end-to-end requests (release build, device idle on Wi-Fi). Prefetch makes the difference far larger still, but it's not where the win comes from.
9+
These results are without prefetch. A common misconception is that nitro-fetch is only faster when you prefetch - it isnt. Plain fetch is faster on its own; in our testing around 15–25% faster than React Natives built-in fetch for end-to-end requests (Android, Samsung F14, release build, device idle on Wi-Fi). Prefetch makes the difference far larger still, but its not where the win comes from.
1010

1111
How much faster depends heavily on how your backend is set up — connection reuse, HTTP/2, and especially **HTTP/3 over QUIC** widen the gap.
1212

0 commit comments

Comments
 (0)