From f42b28f99df01084eaf91e307d1386f76581f6bb Mon Sep 17 00:00:00 2001
From: Long Hoang <1732217+loong@users.noreply.github.com>
Date: Wed, 21 Jun 2023 11:31:44 +0800
Subject: [PATCH] Update critical swap usage threshold

---
 apps/docs/pages/guides/platform/exhaust-ram.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/pages/guides/platform/exhaust-ram.mdx b/apps/docs/pages/guides/platform/exhaust-ram.mdx
index f8af80d83ce..2e5a68e3c96 100644
--- a/apps/docs/pages/guides/platform/exhaust-ram.mdx
+++ b/apps/docs/pages/guides/platform/exhaust-ram.mdx
@@ -23,7 +23,7 @@ You may observe elevated memory usage even when your database has little to no l
 
 Every Supabase project runs in its own dedicated virtual machine. Your instance will have a different set of hardware provisioned depending on your [compute add-on](https://supabase.com/docs/guides/platform/compute-add-ons). Depending on your workload, your compute hardware may not be suitable and can result in high RAM usage.
 
-A good proxy for unhealthy memory usage is swap usage. If you run out of RAM, your system will offload memory to your disk's much slower swap partition. If your swap is above 40%, chances are high that your compute hardware is not suitable for your workload. Head over to your project's [Database Health](https://supabase.com/dashboard/project/_/reports/database) to see your swap usage.
+A good proxy for unhealthy memory usage is swap usage. If you run out of RAM, your system will offload memory to your disk's much slower swap partition. If your swap is above 70%, chances are high that your compute hardware is not suitable for your workload. Head over to your project's [Database Health](https://supabase.com/dashboard/project/_/reports/database) to see your swap usage.
 
 High RAM usage could come with a range of issues: