Single-threaded but can run multiple processes, it can be fully utilized. It depends on how many cores your machine has
For online deployment, you can look at pm2. Generally speaking, node deployment is in master-slave mode. One master process has several sub-processes. For example, the one we use is older, forever, and the master is responsible for monitoring. , if the child process hangs, the master will restart it, and there will be no so-called single point of failure
I haven’t deactivated the cloud server, so it’s not easy to answer
This article can help you understand
http://f2e.souche.com/blog/no...
Single-threaded but can run multiple processes, it can be fully utilized. It depends on how many cores your machine has
For online deployment, you can look at pm2. Generally speaking, node deployment is in master-slave mode. One master process has several sub-processes. For example, the one we use is older, forever, and the master is responsible for monitoring. , if the child process hangs, the master will restart it, and there will be no so-called single point of failure
I haven’t deactivated the cloud server, so it’s not easy to answer