Hi Dave,
> Why not just increase the size of your runtime heap? The instructions are in
> issue 2142.
I've read the workaround, but the software is open source and it would
be a pain to force any users to recompile Go on their machines and
also, the use of RPC means that the system can be distributed over a
number of machines, which potentially makes the cost of using 32 GB
rather than 64GB machines on the likes of EC2 a bit more flexible.
I'm fairly sure that renaming processes would be useful in other use
cases too...
I see that the 16GB issue is flagged as a Go 1.1 milestone, is it
possible that this could be an environment variable flag in an earlier
release?
Cheers,
Donovan.