iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A Kooboo-reported benchmark put 5,000 separately editable site instances on one 2-vCPU, 4-GB Tencent Cloud Lighthouse server. In a separate test, 99.001% of 200,000 warm server renders of a dynamic page querying ten blog items finished in less than 1 ms. Those are two different results: the first measures public-Internet HTTPS requests to site homepages; the second times server rendering only, not a visitor’s full page load.
What the two benchmarks actually tested
Kooboo reported both tests in 2026, but they used different workloads and measurement boundaries. The capacity test exercised requests to 5,000 site instances. The render test measured the time taken to prepare a specific dynamic page response inside the server. Neither result should be read as a general guarantee for any 5,000-site deployment or as a sub-millisecond browser experience.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
ZOERAX 100-Pack M6 x 16mm Rack Mount Cage Nuts, Screws and Washers | $23.99 | Buy on Amazon |
| Benchmark | What it measured | What it did not establish |
|---|---|---|
| Capacity | Public-Internet HTTPS requests for the root page across 5,000 Kooboo site instances on one server. | That arbitrary production sites, heavier workloads, or another provider will fit or perform identically. |
| Rendering | Warm server-side rendering of a dynamic page that queried ten blog items. | End-to-end browser load time, Internet latency, or maximum-throughput capacity. |
How the capacity test was configured
Kooboo’s capacity report says the team imported one controlled site package 5,000 times, assigning every instance a distinct site name and hostname. Each site had its own editable content and identity, but all shared one Kooboo process and originated from the same package. “Independent” here means separately managed Kooboo site records, not separate virtual machines or operating-system processes.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe package contained ten AI-generated blog articles, a dynamic home-page blog query, layouts and views, routes, and article detail pages. The capacity run requested only each site’s root page, rather than testing every route or editing content during the run. The report describes the target as a 2-vCPU, 4-GB Tencent Cloud Lighthouse instance in Virginia running Ubuntu 24.04.4 LTS on a shared 200-Mbps network plan. A separate load generator in Silicon Valley sent HTTPS requests over the public Internet. The run began September 5, 2026 at 12:15:51 UTC and aimed to start 150 requests per second for ten minutes. Kooboo’s capacity benchmark report.
#1 Best Overall
- Wide Compatibility & Versatile Use: ZOERAX M6 rack mount screw kit is ideal for installing server racks, network cabinets, rack shelves, patch panels, A/V equipment, and more. Designed for standard square-hole racks and cabinets, these M6 cage nuts and screws ensure a secure fit for most 19-inch rack systems used in data centers, offices, and home labs
- Heavy-Duty Carbon Steel Construction: Made from premium carbon steel, these M6 cage nuts and screws deliver high strength and long-lasting durability. The material provides excellent resistance to rust, corrosion, and oxidation, performing reliably in demanding environments such as high humidity, temperature fluctuations, and long-term rack installations
- Precision Metric Standard M6: Manufactured to strict metric standards, each M6 screw and cage nut features precise dimensions with minimal tolerance. Clean, sharp threads without burrs allow smooth installation without stripping or slipping. The deep Phillips head design ensures better torque control and faster, more efficient mounting
- Safe, Reliable & Eco-Conscious Materials: ZOERAX uses non-toxic, environmentally friendly carbon steel materials to ensure safe handling and use. Heat-treated for optimal hardness, ductility, and impact resistance, these rack screws and cage nuts offer dependable performance while meeting safety and quality expectations for professional installations
- Complete Mounting Kit with Washers: This essential M6 rack hardware kit includes screws, cage nuts, and heavy-duty washers. The included washers help distribute pressure evenly and reduce scratches or marks on rack rails and equipment, providing a cleaner, more secure installation right out of the box
What happened under the capacity load
The planned request count was 90,000. Kooboo reported 89,969 verified successful responses: a 99.97% first-attempt success rate, with 31 connection timeouts, zero HTTP errors, and zero content mismatches. The report attributes the timeouts to ten-second connection-establishment timeouts without an HTTP response, but does not assign them to a particular provider.
- Request starts: 146.59 per second measured against a configured target of 150 per second.
- Complete-content latency: p50 296.73 ms, p95 1,431.27 ms, and p99 3,393.82 ms.
- Resource use: average Kooboo CPU use was 45.6% of total two-vCPU capacity; sampled peak CPU was 81.5%; sampled peak resident memory was approximately 2.50 GiB.
These are network-inclusive measurements. They include request scheduling, DNS, connection establishment, TLS, routing, application work, and response transfer. The test downloaded each response body and checked for the expected numbered site marker, so a successful HTTP status from the wrong site would not count as correct. The results support a claim about this controlled workload, not a blanket capacity figure for sites with different content, databases, commerce features, API traffic, or write-heavy activity. Kooboo’s capacity benchmark report.
What “under 1 ms” means in the rendering test
In a separate report, Kooboo measured 200,000 verified renders across 5,000 sites in two controlled runs, using one and two closed-loop workers. Each request dynamically queried and displayed ten blog items. The page cache and full-page output cache were disabled, while the reusable Header View retained Kooboo’s cache-by-purpose feature. Each site received a warm-up request before its run.
Free tools Windows power users keep installed
One-click scans. No signup required.
- 196,609 of 200,000 renders (98.3045%) completed below 0.5 ms.
- 198,002 of 200,000 renders (99.001%) completed below 1 ms.
- Combined server-render latency was p50 0.306 ms, p95 0.443 ms, and p99 0.991 ms.
- In the two-worker run alone, p50 was 0.302 ms and p95 was 0.441 ms, but p99 was 1.347 ms.
The timer stopped before response writing. It excluded DNS, TCP, TLS, Internet routing, compression, and client download. So the sub-millisecond result is not the time for a browser to load the page. In the render test’s separate public-network measurements, complete-content latency was p50 15.949 ms and p95 90.317 ms. That difference is expected: a server-render timer and a downloaded response measure different parts of a request. Kooboo’s rendering benchmark report.
Why this was a latency test, not a saturation test
Each worker waited for a full response before starting another request, making this a low-concurrency latency test rather than a maximum-throughput test. The requests used one HTTPS transport host with changing Host headers, avoiding the DNS and connection churn that would come from using 5,000 separate domains. The result therefore does not establish how the same instance would behave under high concurrency, cold execution, or a different network path.
Reproducing the exact render measurement
Kooboo’s report says the Server-Timing instrumentation used for the precise server-side timing was available only on a dedicated 1MsRenderTest source branch at commit b50c7505f758d634a945ccccf71bcd50c5ce5f2e when the report was written, not on the public release or master branch. Reproducing that timing therefore required the instrumented build or a later release that included the instrumentation. Kooboo’s rendering benchmark report.
How Kooboo explains the result
Kooboo CEO and benchmark author Guoqi Zheng describes the product as integrating its web server, database engine, and render engine in one system. In his account, this avoids process boundaries and intermediate serialization in the request path. Kooboo also prepares a page plan before a request arrives, then executes that prepared sequence with request-specific data. The implementation account says much of the output stays in byte arrays and is written as UTF-8 to reduce repeated string allocation and conversion.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →These are the vendor’s explanations of design intent, not independent proof that any single design choice caused the benchmark result or that it outperforms another framework. Zheng summarizes the goal as: “The goal was to remove unnecessary work from the hot path.” Kooboo’s benchmark overview and design explanation.
What a site owner should take from the numbers
The test demonstrates that a small server can serve a narrowly defined set of many lightweight, similarly structured Kooboo sites while rendering a real dynamic query. It is useful evidence for that scenario, not a sizing formula. Before using it to plan a deployment, compare your workload against the test on the factors that materially affect capacity:
- How many sites and how much variation there is in their content, routes, data, and features.
- Request rate and concurrency, not just site count.
- Warm versus cold execution and the cache behavior of each page component.
- Whether the measured latency is server rendering, time to first byte, or complete response delivery.
- Network and geography, including DNS, TLS, and the distance between visitors and the server.
- Whether the workload includes edits, writes, large databases, commerce, or API traffic.
All figures in these reports are Kooboo-reported results for the stated setup. The reports do not provide an independent industry-wide statistic or a comparison with another web framework.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
