On Mon, Aug 12, 2024 at 6:17 AM Robert Engels <reng...@ix.netcom.com> wrote: > > Revisiting an old thread > https://groups.google.com/g/golang-nuts/c/jPb_h3TvlKE/m/qdoHhxXeAwAJ > > Is it still the case that high disk IO throughput requires a GOMAXPROCS > seething higher than the number of cpus on the system?
It's true that we don't use the poller for local file operations on most systems. So if your program is overloading the file system, it is possible for goroutines to be delayed waiting for file I/O to finish. Those delays won't be for long, as the scheduler will step in and start new threads as needed. However, it won't do that right away; I think the delay can be up to 10ms. In such a case it can be useful to increase GOMAXPROCS to permit queuing up more file I/O more quickly, or to do other non-I/O related activity. > Are there any other cases where this might be required? Not that I'm aware of. Ian -- 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/CAOyqgcWDmT-8T4hZcyP9Oo0dD3bxWYb_7Q5fVOYbYx2BWahE8A%40mail.gmail.com.
