From 60a4b158d8046bb65953048beef0ed0077182ebd Mon Sep 17 00:00:00 2001 From: Alexander Karan <47707063+AlexanderKaran@users.noreply.github.com> Date: Fri, 30 Oct 2026 11:49:04 +0800 Subject: [PATCH 1/3] Initial copy changes --- .../benchmarks/ssr-load-test/Description.mdx | 9 +++++---- .../ssr-router-link-load-test/Description.mdx | 7 ++++--- packages/docs/src/components/setup/RunTimeSetup.mdx | 10 ++++++---- 3 files changed, 15 insertions(+), 11 deletions(-) diff --git a/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx b/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx index 32ecc641..8973301a 100644 --- a/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx +++ b/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx @@ -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 -`` 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. +Each app renders a table and connects/requests are slowly increased. We have two versions of this tests. + +In the first one, we use only normal `` tags to ensure a meta-frameworks link component adds no extra work. + +To see how a meta-frameworks link component can affect rendering, we have [re-done this test using framework link components](/run-time/#ssr-router-link-load-test) diff --git a/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx b/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx index 0ca266fc..5e512136 100644 --- a/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx +++ b/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx @@ -1,4 +1,5 @@ -Methodology: [SSR Router Link Load Test](/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. +The same load test as before, but using each meta-framework's router link component. Shows how rendering these can affect performance. + +If a meta-framework lacks a link component, it is excluded. \ No newline at end of file diff --git a/packages/docs/src/components/setup/RunTimeSetup.mdx b/packages/docs/src/components/setup/RunTimeSetup.mdx index 73f72802..a0ca90cb 100644 --- a/packages/docs/src/components/setup/RunTimeSetup.mdx +++ b/packages/docs/src/components/setup/RunTimeSetup.mdx @@ -1,4 +1,6 @@ -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. + From cef1b555f8318f66e405daf6828550a1975fbfd0 Mon Sep 17 00:00:00 2001 From: Alexander Karan <47707063+AlexanderKaran@users.noreply.github.com> Date: Fri, 30 Oct 2026 11:51:53 +0800 Subject: [PATCH 2/3] Few more tweaks --- .../server-side-throughput-tests/Description.mdx | 2 ++ .../components/benchmarks/ssr-load-test/Description.mdx | 6 +++--- .../benchmarks/ssr-router-link-load-test/Description.mdx | 8 +++++--- 3 files changed, 10 insertions(+), 6 deletions(-) diff --git a/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx b/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx index 5fc4390c..ce35dbf6 100644 --- a/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx +++ b/packages/docs/src/components/benchmarks/server-side-throughput-tests/Description.mdx @@ -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. diff --git a/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx b/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx index 8973301a..5e38c6b9 100644 --- a/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx +++ b/packages/docs/src/components/benchmarks/ssr-load-test/Description.mdx @@ -1,7 +1,7 @@ Methodology: [SSR Load Test](/methodology/#ssr-load-test). -Each app renders a table and connects/requests are slowly increased. We have two versions of this tests. +Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table. -In the first one, we use only normal `` tags to ensure a meta-frameworks link component adds no extra work. +This version uses ordinary `` links to measure server rendering without the extra work of rendering framework router link components. -To see how a meta-frameworks link component can affect rendering, we have [re-done this test using framework link components](/run-time/#ssr-router-link-load-test) +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. diff --git a/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx b/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx index 5e512136..4b0d28a3 100644 --- a/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx +++ b/packages/docs/src/components/benchmarks/ssr-router-link-load-test/Description.mdx @@ -1,5 +1,7 @@ -Methodology: SSR Router Link Load Test. +Methodology: [SSR Router Link Load Test](/methodology/#ssr-router-link-load-test). -The same load test as before, but using each meta-framework's router link component. Shows how rendering these can affect performance. +Measures server throughput and response latency as concurrent connections increase, with each request rendering a 1,000-row table using framework router link components. -If a meta-framework lacks a link component, it is excluded. \ No newline at end of file +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. From c200deb10634c865cf3ab1c3529cd1a2585f638a Mon Sep 17 00:00:00 2001 From: Alexander Karan <47707063+AlexanderKaran@users.noreply.github.com> Date: Fri, 30 Oct 2026 12:09:24 +0800 Subject: [PATCH 3/3] Deleted space --- packages/docs/src/components/setup/RunTimeSetup.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/packages/docs/src/components/setup/RunTimeSetup.mdx b/packages/docs/src/components/setup/RunTimeSetup.mdx index a0ca90cb..36600fb0 100644 --- a/packages/docs/src/components/setup/RunTimeSetup.mdx +++ b/packages/docs/src/components/setup/RunTimeSetup.mdx @@ -3,4 +3,3 @@ 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. -