Speed up SAST analyzer nodejs-scan
nodejs-scan MR !20 upgraded Babel to 7.7 which has had some negative effects on the amount of time it takes to run the analyzer.
A few items to investigate are:
-
Parallelizing babel and results -
Use stdin/stdout with babel to scan js -
We currently loop the filesystem multiple times. Do we need to do that each time?
Before digging into that, we need to setup a way to benchmark a baseline before moving towards improvements.
-
Make sure that the test suite is setup to utilize the golang --benchmark flag -
Pick and post a specific commit for the gitlab repo to test against so that results posted here can be as reproducible as possible.
repo: https://gitlab.com/gitlab-org/security-products/analyzers/nodejs-scan
Edited by Daniel Paul Searles