Heavyweight threads are real threads in the operating system, and users do not have strong control over them
Lightweight threads are actually pseudo-threads. Users have more control over it, and the same is true for coroutines in golang: they are scheduled by the go language itself.
Processes and threads are concepts that can be identified at the operating system level, which means that processes and threads can find corresponding IDs in the operating system. That is, heavyweight. Coroutines are finer-grained units of work than threads. There is also the concept of coroutine in java: http://www.blogjava.net/BlueD...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Heavyweight threads are real threads in the operating system, and users do not have strong control over them
Lightweight threads are actually pseudo-threads. Users have more control over it, and the same is true for coroutines in golang: they are scheduled by the go language itself.
Processes and threads are concepts that can be identified at the operating system level, which means that processes and threads can find corresponding IDs in the operating system. That is, heavyweight.
Coroutines are finer-grained units of work than threads.
There is also the concept of coroutine in java: http://www.blogjava.net/BlueD...