NestJS Enterprise Backend APIs · 课时

数据库性能监控

利用 Supabase 工具和 PostgreSQL 功能监控数据库性能、识别瓶颈并跟踪关键指标

数据库性能监控 是 CoddyKit 上的免费 NestJS Enterprise Backend APIs 课时。这是第 2 节课，共 6 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 NestJS Enterprise Backend APIs 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 NestJS Enterprise Backend APIs 课程共包含 6 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Monitor Database Performance?

Imagine your app suddenly feels slow. Users are complaining, and operations are timing out. Database performance monitoring is your diagnostic tool!

It helps you:

Identify slow queries causing bottlenecks.
Understand resource usage (CPU, RAM).
Prevent outages by spotting issues early.
Optimize your database for speed and efficiency.

Key Performance Indicators (KPIs)

To monitor effectively, you need to know what to look for. These are your key performance indicators:

CPU Usage: How much processing power your database is using. High CPU can mean complex queries or too many connections.
Memory Usage: How much RAM is consumed. Excessive usage can lead to slower disk I/O.
Disk I/O: The rate at which data is read from and written to disk. High I/O can indicate inefficient queries or missing indexes.
Active Connections: The number of clients currently connected to your database. Too many can overwhelm the server.
Query Latency: The time it takes for queries to execute. This directly impacts user experience.

Supabase Dashboard: Metrics Overview

Supabase provides built-in monitoring tools right in your project dashboard. Navigate to the 'Metrics' section to see a high-level overview of your database's health.

Here you'll find graphs and charts for CPU, memory, network, and disk usage. This is your first stop for a quick health check!

Dashboard: Resource Graphs Deep Dive

The 'Metrics' section details historical performance. Look for:

CPU Usage: Spikes often correlate with heavy query loads.
Memory Usage: A steady increase might indicate memory leaks or inefficient caching.
Disk I/O: High read/write activity can point to queries scanning large tables without proper indexes.
Network Usage: Shows data transfer in and out, useful for understanding client-server communication load.

Analyzing trends over time helps you understand normal behavior and spot anomalies.

Dashboard: Query Performance Insights

Beyond resource graphs, the Supabase dashboard often includes a 'Query Performance' or 'Insights' section. This tool is invaluable for identifying your slowest queries.

It aggregates data on query execution times, frequency, and total time spent. This allows you to quickly pinpoint which SQL statements are consuming the most resources and need optimization.

PostgreSQL: pg_stat_activity

For real-time insights into what your database is doing *right now*, you can use PostgreSQL's pg_stat_activity view. It shows every active connection and the query it's currently running (or waiting on).

This is great for spotting long-running queries or connections that are idle in transaction.

SELECT
  pid,
  datname,
  usename,
  state,
  query_start,
  query
FROM pg_stat_activity
WHERE state = 'active'
ORDER BY query_start DESC;

PostgreSQL: pg_stat_statements

While pg_stat_activity is for real-time, pg_stat_statements helps you track *historical* aggregated statistics for all executed queries. It's an extension that you enable.

It records metrics like total execution time, call count, and standard deviation for each unique query, making it perfect for finding consistently slow queries over time.

Enabling and Using pg_stat_statements

To use pg_stat_statements, you first need to enable it in your Supabase project's database settings (under Extensions) or via SQL in the SQL Editor.

After enabling, run some queries, then query the view to see the stats:

CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

SELECT
  query,
  calls,
  total_time,
  mean_time,
  stddev_time
FROM pg_stat_statements
ORDER BY total_time DESC
LIMIT 10;

Interpreting pg_stat_statements Results

When examining pg_stat_statements output, focus on:

total_time: Queries with the highest total execution time are your primary targets for optimization.
mean_time: High average execution time indicates a consistently slow query.
calls: A frequently called query, even if fast, can contribute significantly to overall load if its total_time is high.

Use these insights to identify which queries need attention, perhaps by adding indexes or rewriting them.

Monitoring Tools Check

You've learned about various tools and metrics for monitoring your Supabase database. Let's test your knowledge!

Recap: Keeping Your Database Healthy

In this lesson, we explored how to monitor your Supabase database's performance. We covered:

The importance of monitoring and key KPIs like CPU, memory, and query latency.
Utilizing the Supabase Dashboard's Metrics and Query Performance sections.
Leveraging powerful PostgreSQL views like pg_stat_activity for real-time insights.
Implementing and interpreting pg_stat_statements for historical query analysis.

Regular monitoring helps you proactively maintain a fast and responsive application. Next up, we'll dive into optimizing those slow queries!

常见问题解答

「数据库性能监控」课时是免费的吗？

是的 — 「数据库性能监控」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 NestJS Enterprise Backend APIs 课程的其余内容，请升级到 CoddyKit PRO。 NestJS Enterprise Backend APIs 课程共包含 6 节课。

「数据库性能监控」这节课中我会学到什么？

利用 Supabase 工具和 PostgreSQL 功能监控数据库性能、识别瓶颈并跟踪关键指标你通过在浏览器中直接运行的动手代码来练习 NestJS Enterprise Backend APIs，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 NestJS Enterprise Backend APIs 需要有经验吗？

无需任何先前经验。CoddyKit 上的 NestJS Enterprise Backend APIs 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 6 节。

「数据库性能监控」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 NestJS Enterprise Backend APIs 课中编写并运行代码吗？

能。每节 NestJS Enterprise Backend APIs 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 NestJS Enterprise Backend APIs