[go-nuts] Re: GOMAXPROCS > num of CPU

2019-12-21 Thread Didier Spezia
You may be interested in this thread started by the Badger people: https://groups.google.com/d/msg/golang-nuts/jPb_h3TvlKE/qdoHhxXeAwAJ Apparently it can be used to increase the throughput of concurrent disk I/O heavy programs. Regards, Didier. On Thursday, December 5, 2019 at 10:51:50 AM

[go-nuts] Re: GOMAXPROCS > num of CPU

2019-12-05 Thread Vincent Blanchon
Hello Serhat, Yes, I do not see a use case either. This is why I opened this thread, to know if someone sees a use case since it has been mentioned on GitHub :) Le jeudi 5 décembre 2019 11:33:10 UTC+4, Serhat Şevki Dinçer a écrit : > > In runtime it says: > > The GOMAXPROCS variable limits

[go-nuts] Re: GOMAXPROCS > num of CPU

2019-12-04 Thread Serhat Şevki Dinçer
In runtime it says: 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 blocked in system calls on behalf of Go code; those do not count against the GOMAXPROCS limit.