On Sun, Jul 31, 2016 at 5:44 PM Brad Fitzpatrick <bradf...@golang.org> wrote:
> You should expect at most 10ms pauses for large heaps as of Go 1.6, and especially in Go 1.7. I'm assuming those 10ms are valid for most/typical programs and that the worst case of some, still perfectly reasonable programs[0], cannot be guaranteed to be on average that low[1]. Is that assumption correct? [0]: Let's imagine for example a program repeatedly producing a tiny sized node single linked list of size, say 32GB, doing something with it and throwing it away afterwards for the GC to deal with it. [1]: Or the pause must move instead to malloc waiting for the GC to free memory, so technically it's not [directly] a GC pause. -- -j -- 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.
