diff --git a/apps/docs/pages/guides/platform/performance.mdx b/apps/docs/pages/guides/platform/performance.mdx index 609a303d26f..8dbe236cc52 100644 --- a/apps/docs/pages/guides/platform/performance.mdx +++ b/apps/docs/pages/guides/platform/performance.mdx @@ -124,7 +124,7 @@ Queries which are the most time consuming are not necessarily bad, you may have Generally for most applications a small percentage of data is accessed more regularly than the rest. To make sure that your regularly accessed data is available, Postgres tracks your data access patterns and keeps this in its [shared_buffers](https://www.postgresql.org/docs/15/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-MEMORY) cache. -Applications with lower cache hit rates generally perform more poorly since they have to hit the disk to get results rather than serving them from memory. Very poor hit rates can also cause you to burst past your [Disk I/O limits](https://supabase.com/docs/guides/platform/compute-add-ons#disk-io-bandwidth) causing significant performance issues. +Applications with lower cache hit rates generally perform more poorly since they have to hit the disk to get results rather than serving them from memory. Very poor hit rates can also cause you to burst past your [Disk I/O limits](https://supabase.com/docs/guides/platform/compute-add-ons#disk-throughput-and-iops) causing significant performance issues. You can view your cache and index hit rate by executing the following query: diff --git a/apps/docs/pages/guides/platform/troubleshooting.mdx b/apps/docs/pages/guides/platform/troubleshooting.mdx index 5ac27b8b71d..5e4b244192b 100644 --- a/apps/docs/pages/guides/platform/troubleshooting.mdx +++ b/apps/docs/pages/guides/platform/troubleshooting.mdx @@ -31,7 +31,7 @@ Some common solutions for this issue are: - [Using fewer Postgres connections](../platform/performance#configuring-clients-to-use-fewer-connections) can reduce the amount of resources needed on the project. - [Restarting](https://app.supabase.com/project/_/settings/general) the database. This only temporarily solves the issue by terminating any ongoing workloads that might be tying up your compute resources. -If your [Daily Disk IO budget](../platform/compute-add-ons#disk-io-bandwidth) has been drained, you will need to either wait for it to be replenished the next day, or upgrade to a larger compute add-on to increase the budget available to your project. +If your [Daily Disk IO budget](../platform/compute-add-ons#disk-throughput-and-iops) has been drained, you will need to either wait for it to be replenished the next day, or upgrade to a larger compute add-on to increase the budget available to your project. ## Unable to connect to your Supabase Project diff --git a/studio/components/interfaces/BillingV2/Subscription/AddOns/AddOns.tsx b/studio/components/interfaces/BillingV2/Subscription/AddOns/AddOns.tsx index b66ef1fbe3c..86352c7d1e4 100644 --- a/studio/components/interfaces/BillingV2/Subscription/AddOns/AddOns.tsx +++ b/studio/components/interfaces/BillingV2/Subscription/AddOns/AddOns.tsx @@ -221,7 +221,7 @@ const AddOns = ({}: AddOnsProps) => {
{computeInstanceSpecs?.connections_pooler ?? 200}
@@ -240,7 +240,7 @@ const AddOns = ({}: AddOnsProps) => {
diff --git a/studio/components/interfaces/BillingV2/Subscription/Tier/EnterpriseCard.tsx b/studio/components/interfaces/BillingV2/Subscription/Tier/EnterpriseCard.tsx index f087cf8687d..f3ef23e63be 100644 --- a/studio/components/interfaces/BillingV2/Subscription/Tier/EnterpriseCard.tsx +++ b/studio/components/interfaces/BillingV2/Subscription/Tier/EnterpriseCard.tsx @@ -39,7 +39,7 @@ const EnterpriseCard = ({ plan, isCurrentPlan, isTeamTierEnabled }: EnterpriseCa diff --git a/studio/components/interfaces/BillingV2/Usage/Activity.tsx b/studio/components/interfaces/BillingV2/Usage/Activity.tsx index a5e7ef7af2a..987f30d3fff 100644 --- a/studio/components/interfaces/BillingV2/Usage/Activity.tsx +++ b/studio/components/interfaces/BillingV2/Usage/Activity.tsx @@ -176,7 +176,7 @@ const Activity = ({ projectRef }: ActivityProps) => {
{attribute.name} quota usage
+{attribute.name} usage
{!usageBasedBilling && usageRatio >= 1 ? (Used
++ {attribute.chartPrefix || 'Used '}in period +
{(usageMeta?.usage ?? 0).toLocaleString()}
{attribute.name} over time
+{attribute.name} per day
{attribute.chartDescription.split('\n').map((paragraph, idx) => ({paragraph} @@ -269,15 +271,12 @@ const Activity = ({ projectRef }: ActivityProps) => {
{attribute.name} quota usage
+{attribute.name} usage
{!usageBasedBilling && usageRatio >= 1 ? (Used
++ {attribute.chartPrefix || 'Used '}in period +
{formatBytes(usageMeta?.usage ?? 0)}
{attribute.name} over time
+{attribute.name} per day
{attribute.chartDescription.split('\n').map((paragraph, idx) => ({paragraph} @@ -183,15 +185,12 @@ const Bandwidth = ({ projectRef }: BandwidthProps) => {
- Your workload has used up all the burst IO throughput minutes during the day - and is running at the baseline performance. If you need consistent disk - performance, consider upgrading to a larger compute add-on. + Your workload has used up all the burst IO throughput minutes and ran at the + baseline performance. If you need consistent disk performance, consider + upgrading to a larger compute add-on.
@@ -133,7 +132,7 @@ const Infrastructure = ({ projectRef }: InfrastructureProps) => {Your workload is about to use up all the burst IO throughput minutes during @@ -185,24 +184,17 @@ const Infrastructure = ({ projectRef }: InfrastructureProps) => { )}
IO Budget remaining
+ {attribute.key === 'disk_io_consumption' ? ( +IO consumed per day
) : (Max{' '} {attribute.name} {' '} - usage + per {interval === '1d' ? 'day' : 'hour'}
)} - - - - -{attribute.name} quota usage
+{attribute.name} usage
{!usageBasedBilling && usageRatio >= 1 ? (Used
++ {attribute.chartPrefix || 'Used '}in period +
{attribute.unit === 'bytes' ? formatBytes(usageMeta?.usage ?? 0) @@ -217,7 +219,10 @@ const SizeAndCounts = ({ projectRef }: SizeAndCountsProps) => { )}
{attribute.name} over time
++ {attribute.chartPrefix || ''} + {attribute.name} per day +
{attribute.chartDescription.split('\n').map((paragraph, idx) => ({paragraph} @@ -232,15 +237,12 @@ const SizeAndCounts = ({ projectRef }: SizeAndCountsProps) => {