I'd also assume that `GOMAXPROCS=1` doesn't disable the preemptive
scheduling of goroutines in recent Go versions - I believe
`GODEBUG=asyncpreemptoff=1` is required for that.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from
Hi,
another thing to keep in mind is that `GOMAXPROCS=1` does not actually make
your program single-threaded:
The GOMAXPROCS variable limits the number of operating system threads that
> can execute user-level Go code simultaneously. There is no limit to the
> number of threads that can be blocke
On Sun, Nov 1, 2020 at 9:15 PM Ting Yuan wrote:
> I find it is tricky to debug a concurrency Go program in multi-core
> systems, so I wonder if there is a way to make the program run in
> deterministically. Can I assume a program with GOMAXPROCS(1) can be
> deterministically
> executed ?
>
In a
Hello,
> I find it is tricky to debug a concurrency Go program in multi-core
> systems, so I wonder if there is a way to make the program run in
> deterministically. Can I assume a program with GOMAXPROCS(1) can be
> deterministically
> executed ?
Even with GOMAXPROCS=1, a Go program is not 100%
I find it is tricky to debug a concurrency Go program in multi-core
systems, so I wonder if there is a way to make the program run in
deterministically. Can I assume a program with GOMAXPROCS(1) can be
deterministically
executed ?
Here a deterministic execution means once the input is given,
