From 2752e2fbe41bee90b70547d2c73c2b676abb3ecf Mon Sep 17 00:00:00 2001
From: Jon Harrell <4829245+jharrell@users.noreply.github.com>
Date: Mon, 1 Apr 2024 11:40:17 -0500
Subject: [PATCH] resolves DA-173
---
docs/300-accelerate/250-connection-pooling.mdx | 4 +++-
docs/300-accelerate/300-caching.mdx | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/docs/300-accelerate/250-connection-pooling.mdx b/docs/300-accelerate/250-connection-pooling.mdx
index 007dde554f..2e702f4c95 100644
--- a/docs/300-accelerate/250-connection-pooling.mdx
+++ b/docs/300-accelerate/250-connection-pooling.mdx
@@ -4,7 +4,7 @@ metaTitle: 'Accelerate: Connection Pooling'
metaDescription: "Learn about everything you need to know to use Accelerate's connection pooling."
---
-## Connection pooling
+
A [connection pool](https://en.wikipedia.org/wiki/Connection_pool#:~:text=In%20software%20engineering%2C%20a%20connection,executing%20commands%20on%20a%20database.) is a storage of database connections that can be reused for future requests to the database. When a new connection is requested, it is retrieved from the pool if one is available. Once the connection is no longer needed, it is returned to the pool for reuse.
@@ -20,6 +20,8 @@ For more information about connection pooling in Prisma, see the documentation [
+
+
### Default connection pool size
By default, Accelerate calculates a default connection pool size using the formula `num_physical_cpus * 2 + 1`.
diff --git a/docs/300-accelerate/300-caching.mdx b/docs/300-accelerate/300-caching.mdx
index b02f7f9c81..b85c550f18 100644
--- a/docs/300-accelerate/300-caching.mdx
+++ b/docs/300-accelerate/300-caching.mdx
@@ -4,6 +4,8 @@ metaTitle: 'Accelerate: Caching'
metaDescription: "Learn everything you need to know to use Accelerate's global database caching."
---
+
+
## Cache strategies
For all read queries in Prisma Client, you can define the `cacheStrategy` parameter that configures cache behavior. The cache strategy allows you to define two main characteristics of the cache: