Virtual thread: Difference between revisions

Revision as of 01:55, 8 May 2022

Revision as of 10:10, 22 May 2022

Line 27:

** Because allocating a virtual thread is akin to allocate memory structures, they can be allocated very quickly, like 600,000 per second. This is not possible for OS threads that would crash the host long before this rate

** The quicker ramp-up lessens the need for thread-pools of pre-launched threads to cater for sudden increases in traffic

** In Go, a virtual thread is allocated using a function call preceded by the keyword go. The function call provides a closure of variable values guaranteed to be visible to the to the new goroutine. goroutines have no return value, so a goroutine that returns just disappears

* '''Virtual threads share memory map like OS threads'''