Skip to content

Commit 2df3c81

Browse files
Run time copy (#732)
1 parent c22be5a commit 2df3c81

4 files changed

Lines changed: 17 additions & 10 deletions

File tree

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,3 @@
11
Methodology: [Server Side Throughput Tests](/methodology/#server-side-throughput-tests).
2+
3+
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.
Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
Methodology: [SSR Load Test](/methodology/#ssr-load-test).
22

3-
Each runtime app renders the same 1,000-row, three-column table using ordinary
4-
`<a>` links. This compares server rendering under HTTP load without the extra work
5-
of rendering framework router link components. Requests still pass through each
6-
framework’s server routing. No browser runs and no links are clicked.
3+
Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table.
4+
5+
This version uses ordinary `<a>` links to measure server rendering without the extra work of rendering framework router link components.
6+
7+
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.
Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,7 @@
11
Methodology: [SSR Router Link Load Test](/methodology/#ssr-router-link-load-test).
22

3-
The same load test using framework router link components, showing how rendering
4-
those components affects server performance compared with ordinary HTML links.
3+
Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table using framework router link components.
4+
5+
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.
6+
7+
Frameworks without a router link component are excluded.
Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
1-
Runtime apps implement comparable benchmark routes across frameworks. See [Default
2-
Benchmark Setup](/methodology/#default-benchmark-setup) for the shared environment
3-
and each framework's build tool and adapter. Test-specific differences are
4-
documented in the linked methodology sections below.
1+
Run Time benchmarks use each meta-framework’s `app-*` package.
2+
3+
Currently, each test uses a different route in its app, configured to meet each test's requirements.
4+
5+
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.

0 commit comments

Comments
 (0)