FAQ
When I enable gctrace, I see that Y > X in the "X -> Y MB" part of output.

If X is the size of used heap before GC and Y is the size after, shouldn't
Y always be <=X?

--
Chandra Sekar.S

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

  • James Bardin at Jul 22, 2014 at 1:11 pm

    On Tuesday, July 22, 2014 8:04:31 AM UTC-4, Chandra Sekar S wrote:
    When I enable gctrace, I see that Y > X in the "X -> Y MB" part of output.

    If X is the size of used heap before GC and Y is the size after, shouldn't
    Y always be <=X?

    They're not the before and after sizes [1]:
         X is the "mean size of live heap after the previous GC" and Y is "full
    heap size (including garbage) before the current GC"

    [1]
    https://software.intel.com/en-us/blogs/2014/05/10/debugging-performance-issues-in-go-programs





    --
    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+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/d/optout.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedJul 22, '14 at 12:04p
activeJul 22, '14 at 1:11p
posts2
users2
websitegolang.org

2 users in discussion

James Bardin: 1 post Chandru: 1 post

People

Translate

site design / logo © 2021 Grokbase