Or to answer your question another way; the more allocations your program performs, the higher the GC overhead to clean them up.
Are you asking: is there a way to limit the % CPU the GC is allowed to use? If so, the answer is no, because: 1. If the GC doesn't keep up with the garbage your program produces memory usage grows withou bound. 2. The garbage collector is designed to minimise stop the world pause time, which costs more in CPU time than a traditional high latency, stop the world, concurrent mark sweep collector. -- 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.
