From 17b6ffa25a1aaab8d1d8f78ba3ed828fdf201442 Mon Sep 17 00:00:00 2001 From: Damien Maillard Date: Wed, 10 Apr 2024 23:03:27 +0200 Subject: [PATCH] Update readme.md --- packages/performance-impact/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/performance-impact/readme.md b/packages/performance-impact/readme.md index f567eb5..98f8934 100644 --- a/packages/performance-impact/readme.md +++ b/packages/performance-impact/readme.md @@ -35,5 +35,5 @@ In any case it means you have to wait before knowing the real performance impact ## Recommended approach to catch performance impacts 1. measure some performance metrics -2. Use `@jsenv/performance-impact` to anticipate big variations +2. Big variations can be anticipated and catched by `@jsenv/performance-impact` 3. For small variations, upload performance metrics to a dashboard. Then, periodically watch the dashboard to check performance metrics tendency over time