Skip to content

Run time copy #732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexanderKaran merged 3 commits into from
Oct 30, 2026
Merged

Run time copy #732

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
60a4b15
Initial copy changes
AlexanderKaran Oct 30, 2026
cef1b55
Few more tweaks
AlexanderKaran Oct 30, 2026
c200deb
Deleted space
AlexanderKaran Oct 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...ges/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,3 @@
Methodology: [Server Side Throughput Tests](/methodology/#server-side-throughput-tests).

Measures how many requests each framework's server handler can process per second when rendering a 1,000-row table, and how long each response takes. Requests bypass network overhead to focus on server rendering performance.
9 changes: 5 additions & 4 deletions packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
Methodology: [SSR Load Test](/methodology/#ssr-load-test).

Each runtime app renders the same 1,000-row, three-column table using ordinary
`<a>` links. This compares server rendering under HTTP load without the extra work
of rendering framework router link components. Requests still pass through each
framework’s server routing. No browser runs and no links are clicked.
Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table.

This version uses ordinary `<a>` links to measure server rendering without the extra work of rendering framework router link components.

Compare it with the [router link load test](/run-time/#ssr-router-link-load-test) to see how framework router link components affect server rendering performance.
7 changes: 5 additions & 2 deletions packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,7 @@
Methodology: [SSR Router Link Load Test](/methodology/#ssr-router-link-load-test).

The same load test using framework router link components, showing how rendering
those components affects server performance compared with ordinary HTML links.
Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table using framework router link components.

Compare it with the [plain link load test](/run-time/#ssr-load-test) to see how these components affect server rendering performance. These tests make HTTP requests only; they do not measure browser navigation or prefetching.

Frameworks without a router link component are excluded.
9 changes: 5 additions & 4 deletions packages/docs/src/components/setup/RunTimeSetup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
Runtime apps implement comparable benchmark routes across frameworks. See [Default
Benchmark Setup](/methodology/#default-benchmark-setup) for the shared environment
and each framework's build tool and adapter. Test-specific differences are
documented in the linked methodology sections below.
Run Time benchmarks use each meta-framework’s `app-*` package.

Currently, each test uses a different route in its app, configured to meet each test's requirements.

See [Default Benchmark Setup](/methodology/#default-benchmark-setup) for the base set-up. Each test's specific setup is linked in the methodology with links in each section.
Loading