On Tue, May 16, 2017 at 8:04 PM, Manish Rai Jain <manishrj...@gmail.com> wrote: > > Ideally, the disk reads could be happening via libaio, causing the OS > threads to not block, so all goroutines can make progress, increasing the > number of read requests that can be made concurrently. This would then also > ensure that one doesn't need to set GOMAXPROCS to a value greater than > number of cores to achieve higher throughput.
libaio sounds good on paper, but at least on GNU/Linux it's all in user space. In effect it does exactly what the Go runtime does already: it hands file I/O operations off to separate threads. The Go runtime would gain nothing at all by switching to using libaio. 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. For more options, visit https://groups.google.com/d/optout.
