dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-16 22:59:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

Fixed spelling error in performance tuning docs

Browse Source
This commit is contained in:
Kevin Brolly committed 2023-02-21 16:14:28 +00:00
1 parent 630536941a
commit 1b9a643a3f
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/platform/performance.mdx
+1 -1
View File
@@ -114,7 +114,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 significat 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-io-bandwidth) causing significant performance issues.
You can view your cache and index hit rate by executing the following query: