1 | - There is a performance issue but Clinic.js could not accurately categorize it.
|
2 | - Clinic.js may inadvertently be picking up system noise.
|
3 | - Disable any CPU- or Memory-intensive applications.
|
4 | - Use the `--on-port` flag to immediately begin load testing, this is known to reduce the chances of interference.
|
5 | - If an unknown result is consistently produced it is still very likely that there is a performance issue.
|
6 | - Undertake additional diagnosis with the <code class='snippet'>clinic bubbleprof</code> and/or <code class='snippet'>clinic flame</code> commands.
|
7 | - For memory analysis use the [`--inspect`](https://nodejs.org/en/docs/inspector) flag with the Chrome Devtools *Memory* tab.
|