I have an HTTP endpoint that may or may not incur massive disk IO depending
on the incoming request. I do not intent to limit the amount of disk IO
operations and would like the endpoint to run to its full throughput
Effective-Go taught me: "(goroutine) if one should block, such as while
waiting for I/O, others continue to run."
So is it OK to leave the IO operation in the HTTP request handler, and let
Go runtime handle the rest? And how many goroutines does net.http server
use for concurrent requests?
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 email@example.com.
For more options, visit https://groups.google.com/d/optout.