> typical advice in Java-land is to have a young generation in the 5-10 GiB range, whereas our minor heaps are measured in megabytes.
Where does that advice come from? Of what I've seen typical suggested values for the young generation in the jvm and clr is 10-20mb. A young generation measured in gigabytes would defeat the idea of dividing the heap into generations in the first place.
Also, unless you have profiled the gc and know exactly in which steps of the process most time is spent, then you are fumbling in the dark.
Where does that advice come from? Of what I've seen typical suggested values for the young generation in the jvm and clr is 10-20mb. A young generation measured in gigabytes would defeat the idea of dividing the heap into generations in the first place.
Also, unless you have profiled the gc and know exactly in which steps of the process most time is spent, then you are fumbling in the dark.