I was hoping to find a node.js system with a workerpool to handle CPU intensive tasks, but I'm a little confused about cpu usage in multiple routes. A scene is like this:

route1.js:
  const workerpool = require('workerpool');
  const pool = workerpool.pool(__dirname + '/job1.js');
  pool.exec.......
route2.js:
  const workerpool = require('workerpool');
  const pool = workerpool.pool(__dirname + '/job2.js');
  pool.exec.......
route3.js:
  const workerpool = require('workerpool');
  const pool = workerpool.pool(__dirname + '/job3.js');
  pool.exec.......

When node.js uses these three files, they create their own workerpool, and Is this possible since the worker_thread number and its control is implemented internally via node.js Create a threshold problem? And how to use workerpool correctly, thank you very much.