seems to me whats relevant is that the core count is 'below' in the software stack, so transparent, so here it will be 24.
but, like all progs, go progs use what they're told about, so you could 'see' less or you COULD be running inside an emulator that mimics, potentially very slowly, any number. also since the OS is 'just' a program, it too could be running with reserved cores or inside any emulator. (would guess windows will detect and do licence/pricing related restrictions on you though.) On Wednesday, 10 June 2020 21:03:41 UTC+1, joe mcguckin wrote: > > I read somewhere that the default # of GO threads is the number of cores > of the cpu. > > What about where there are multiple cpus? My servers have 2, 6 core > Xeons. With hyper threading, it looks like 24 cores available to Linux. > > Will the GO scheduler schedule GO routines on both CPU's? > > If the scheduler is running on one core, how does it manage to put GO > routines on other cores and/or CPU's? Does it create system threads (or > pthreads) on each of the other > cores and CPU's? Can it pin a thread to a specific core, or are you at the > mercy of the OS thread scheduler? > > Inquiring minds want to know... > > Thanks, > > Joe > -- 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/1b05ce92-7b3b-44cc-8eb3-7b42dca91777o%40googlegroups.com.
