(Tarball) execute JS-X-Ray in separate workers #578
Description
Just an idea at this point, since JS-X-Ray cost most of the CPU bound cost at the moment the idea was to allocate one (or a pool?) of worker threads to execute the scan.
A lot of the total delay come from I/O delay and APIs ratelimit but maybe this could help reduce the overall time positively (IDK maybe 20-30% ?).
A least that's something we have to experiment with