Polish Try Prisma Next section and add Compute/Postgres links (#7951)

* docs(blog): polish Try Prisma Next section, add Compute/Postgres cross-links

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* Update apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

* docs(blog): update cover images and throughput chart

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ankur-arch

apps/blog/content/blog/prisma-next-performance-benchmark/index.mdx

@@ -1,11 +1,11 @@
 ---
-title: "Prisma Next is 50% faster than Prisma 7: a performance deep dive"
+title: "Prisma Next Is ~90% As Fast as Raw PG"
 slug: "prisma-next-performance-benchmark"
 date: "2026-06-11"
 authors:
   - "Serhii Tatarintsev"
-metaTitle: "Prisma Next is 50% faster than Prisma 7 | Benchmark"
-metaDescription: "Prisma Next reaches about 50% higher peak throughput than Prisma 7 and holds latency low under load, closing most of the gap to the raw pg driver while keeping Prisma's type-safe, model-first workflow."
+metaTitle: "Prisma Next Is ~90% As Fast as Raw PG"
+metaDescription: "Prisma Next performance benchmarks achieves ~90% of the raw pg driver's peak throughput, holds latency low under load, and ships as a 148.5 KB gzipped bundle for serverless and edge workloads."
 heroImagePath: "/prisma-next-performance-benchmark/imgs/hero.svg"
 heroImageAlt: "Bar chart showing Prisma Next outperforming Prisma 7 in throughput benchmarks"
 metaImagePath: "/prisma-next-performance-benchmark/imgs/meta.png"
@@ -26,7 +26,7 @@ To see where it stands, we ran the same Postgres workload through three setups:
 - At 6,000 to 7,000 requests/second, a level both can serve, Prisma Next's p95 latency stays around 4 ms while Prisma 7's has already climbed past 40 ms.
 - Prisma Next reaches about **87%** of the raw `pg` driver's peak, while Prisma 7 reaches about **58%**.
 
-It's also about **9× smaller** to ship, which matters for serverless and edge deployments where bundle size drives cold starts. We look at that below.
+Its bundle size gzipped is about **148.5 KB** gzipped, compared to **1.32 MB** for Prisma 7, also about **9× smaller** to ship, which matters for serverless and edge deployments where bundle size drives cold starts. We look at that below.
 
 One note before the numbers: **Prisma 7 is still the version to use in production today.** [Prisma Next is in Early Access](https://pris.ly/pn-ea), and once it's Generally Available you'll be able to run it in production too.
 
@@ -44,7 +44,7 @@ The raw `pg` driver is our baseline: the fastest this machine can talk to the da
 
 This is the main result. As traffic rises, all three lines climb together at first; then Prisma 7 flattens out, while Prisma Next and `pg` keep climbing for thousands more requests per second.
 
-![Throughput over the load test: Prisma 7 flattens out just under 8,000 req/s while Prisma Next and pg keep climbing](/prisma-next-performance-benchmark/imgs/throughput-ramp.svg)
+![Throughput over the load test: Prisma 7 flattens out just under 8,000 req/s while Prisma Next and pg keep climbing](/prisma-next-performance-benchmark/imgs/throughput-ramp.png)
 
 That flat line is the overhead the new foundation was built to reduce. The peak each setup sustains, measured as the average of its busiest 10% of the run, lands here:
 
@@ -95,4 +95,20 @@ A few caveats. This is one benchmark, on one workload and one machine, so result
 
 We've shared [our benchmark repo](https://pris.ly/pn-benchmarks), so you can run it yourself and tell us where we're wrong. We'll keep testing more workloads and tuning as Prisma Next moves toward Prisma 8.
 
-To try Prisma Next today, start with the [Early Access blog post](https://pris.ly/pn-ea). Star and watch [prisma/prisma-next](https://github.com/prisma/prisma-next) on GitHub to follow what ships next, and if you hit a snag, start a thread in [#prisma-next on our Discord](https://pris.ly/discord).
+## Try Prisma Next today
+
+There are two ways to get started. To spin up a complete template app, scaffold one with:
+
+```shell
+bunx create-prisma@next
+```
+
+This sets you up with a [Prisma Postgres](https://www.prisma.io/postgres) database and can deploy the app to [Prisma Compute](https://www.prisma.io/compute), our serverless runtime for Prisma apps, so you can see the bundle-size and cold-start benefits above end to end.
+
+To add Prisma Next to an existing app, run:
+
+```shell
+bunx prisma-next@latest init
+```
+
+To learn more, start with the [Early Access blog post](https://pris.ly/pn-ea). Star and watch [prisma/prisma-next](https://github.com/prisma/prisma-next) on GitHub to follow what ships next, and if you hit a snag, start a thread in [`#prisma-next` on our Discord](https://pris.ly/discord).