No, you must understand that javascript has only one execution thread. As long as it enters the calculation-intensive area, the CPU will be occupied and the entire program will be stuck here. The reason why io can use asynchronous acceleration is that the CPU is not occupied during the delay period of io.
No, asynchronous programming is specifically designed to solve IO-intensive problems. When io is blocked, use asynchronous events to release CPU resources for other tasks.
In essence, asynchronous programming tends to use CPU resources as much as possible, so it is completely meaningless for CPU-intensive programs. . .
Parallel computing and distributed computing should be considered at this time.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
No, you must understand that javascript has only one execution thread. As long as it enters the calculation-intensive area, the CPU will be occupied and the entire program will be stuck here. The reason why io can use asynchronous acceleration is that the CPU is not occupied during the delay period of io.
No, asynchronous programming is specifically designed to solve IO-intensive problems. When io is blocked, use asynchronous events to release CPU resources for other tasks.
In essence, asynchronous programming tends to use CPU resources as much as possible, so it is completely meaningless for CPU-intensive programs. . .
Parallel computing and distributed computing should be considered at this time.