From f49c465b4d95b81d60391fe939399b28df8e9b8a Mon Sep 17 00:00:00 2001 From: msfstef Date: Mon, 9 Dec 2024 16:54:42 +0200 Subject: [PATCH] Update text with figure --- website/blog/posts/2024-12-09-electric-beta-release.md | 4 +++- website/docs/reference/benchmarks.md | 8 +++++--- 2 files changed, 8 insertions(+), 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 index bdc3657a04..627131af06 100644 --- 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: - +
+ +
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 index 670ee76d80..9bab97198a 100644 --- 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 +## 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. - +
+ +
## PGlite