Update text with figure

electric-sql · Dec 9, 2024 · 40d4f28 · 40d4f28
1 parent f876c88
commit 40d4f28
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 4 deletions.
diff --git a/website/blog/posts/2024-12-09-electric-beta-release.md b/website/blog/posts/2024-12-09-electric-beta-release.md
@@ -89,7 +89,9 @@ So many real-time sync systems demo well but break under real load.
 
 Electric has been [engineered from the ground up](/docs/api/http) to handle high-throughput workloads, like [Trigger.dev](https://trigger.dev/launchweek/0/realtime), with low latency and flat resource use. You can stream real-time data to **millions of concurrent users** from a single commodity Postgres:
 
-<ScalabilityChart />
+<figure>
+  <ScalabilityChart />
+</figure>
 
 See our [Scaling a sync engine](#) post and [benchmarks](/docs/reference/benchmarks) page for more details.
 

diff --git a/website/docs/reference/benchmarks.md b/website/docs/reference/benchmarks.md
@@ -134,11 +134,13 @@ Latency rises linearly. Memory usage is relatively flat.
 
 Similar to the diverse write fanout, but with many shapes the write falls into, only one is  actively listened to.
 
-## Cloud <Badge type="warning" text="coming soon" />
+## Cloud
 
-Cloud benchmarks test the performance and scalability of Electric when running behind a CDN.
+Electric is designed to run behind a CDN, using the CDN's request collapsing capability to scale out to millions of concurrent users. The graph below shows the latency and compute resource of a single Electric server using this technique to handle millions of concurrent users.
 
-<ScalabilityChart />
+<figure>
+  <ScalabilityChart />
+</figure>
 
 ## PGlite