From 0e7d8caf10979b46f649ff13d7bdd707e7bf87e4 Mon Sep 17 00:00:00 2001 From: Makena-Wambui Date: Fri, 1 Nov 2024 13:24:48 +0300 Subject: [PATCH] Docs: Added an exaplanation as to what Profiling a Node.js application is. --- apps/site/pages/en/learn/getting-started/profiling.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/apps/site/pages/en/learn/getting-started/profiling.md b/apps/site/pages/en/learn/getting-started/profiling.md index 00d977ef87740..3ac8a481ea5ce 100644 --- a/apps/site/pages/en/learn/getting-started/profiling.md +++ b/apps/site/pages/en/learn/getting-started/profiling.md @@ -5,6 +5,12 @@ layout: learn # Profiling Node.js Applications +Profiling a Node.js application involves measuring its performance by analyzing +the CPU, memory, and other runtime metrics while the application is running. +This helps in identifying bottlenecks, high CPU usage, memory leaks, or slow +function calls that may impact the application's efficiency, responsiveness +and scalability. + There are many third party tools available for profiling Node.js applications but, in many cases, the easiest option is to use the Node.js built-in profiler. The built-in profiler uses the [profiler inside V8][] which samples the stack at