Use Case

As a... user of the Node.js driver
I want... the node driver to proactively monitor its startup memory usage/loading time
So that... I don't experience surprise startup performance issues when upgrading to a new version of the driver

User Impact

• All users would be affected by an increase in startup memory usage, but it would likely affect FAAS users the most (depending on the module caching).

Dependencies

• N/A

Unknowns

• What is the best way to get a consistent metric in CI? When measuring the startup memory/time, should we measure the absolute quantity or relative?

Acceptance Criteria

Implementation Requirements

• Create a performance test to measure startup memory and loading time of the node driver
• Add a new task to the evergreen performance test variant
• Target the dedicated perf test distro
• Output the results into a json format and push it to the analytics backend using `perf.send`

Testing Requirements

• Confirm that the trend chart tab is present in the new CI task

Documentation Requirements

• N/A

Follow Up Requirements

• N/A