connections on TCP. These services are largely routers for an evented
database layers & don't do a whole lot of heavy lifting. After some cursory
research, it looks like my primary limitation it looks like my main
constraint will be the minimum goroutine stack size. At 4KB, 1MM
connections means 4GB RAM for the stack of goroutines which are all blocked
on a single epoll. This seems a bit silly; I could buy servers with more
RAM, but it'd be more useful to improve server density before getting the
I want to try reducing the initial stack size since these threads do very
little work themselves. After some investigation, it seems like this is a
const in the go toolchain. Is this correct? If I fiddle with this constant,
will I destabilize anything else? Would the go community be interested in a
patch that makes the value configurable with a flag to go build?
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 firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.