The pause also tends to not be large. Except for bugs (which do exist and some of them are hard to fix) the goal on a modern fast processor is under 100 microseconds of a thread "pausing". There is a period of time where goroutines will make reduced progress as the garbage collector steals either time slices or a processor(s), but the intent is that this be as concurrent (and parallel) as possible. It's complex -- in some bugs the over-long pause is caused by "bad accounting" where a goroutine simply fails to get credit for the work it does on behalf of garbage collection.
On Monday, October 25, 2021 at 1:12:22 PM UTC-4 ren...@ix.netcom.com wrote: > No, unless they call back into Go. > > On Oct 25, 2021, at 10:43 AM, Amir DER <roc...@gmail.com> wrote: > > Does GC pause affect non-go threads spawned by CGo? > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/7d165522-f261-4391-9708-eb3ace3fb7a2n%40googlegroups.com > > <https://groups.google.com/d/msgid/golang-nuts/7d165522-f261-4391-9708-eb3ace3fb7a2n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a60635a2-fd3e-4921-8640-55600b05b988n%40googlegroups.com.
