Re: PRT memory usage

2017-08-23 Thread Thomas Schatzl
Hi, On Wed, 2017-08-23 at 09:05 -0700, yu.zh...@oracle.com wrote: > If you are using jdk8, try -XX:+PrintHeapAtGC   and -XX:+PrintHeapAtGCExtended if you really want extensive per- region information (at every GC). I do not think there is a switch that prints per-region type summary information

Re: PRT memory usage

2017-08-23 Thread yu.zh...@oracle.com
If you are using jdk8, try -XX:+PrintHeapAtGC On 08/23/2017 04:01 AM, Milan Mimica wrote: pon, 21. kol 2017. u 18:42 Thomas Schatzl > wrote: -Xlog:gc+heap=info gives you the following kind of output: Unrecognized option: -Xlog:gc+heap=info Must be somet

Re: PRT memory usage

2017-08-23 Thread Milan Mimica
pon, 21. kol 2017. u 18:42 Thomas Schatzl wrote: >v dir=3D"ltr">pon, 21. kol 2= 017. u 18:42 Thomas Schatzl thomas.scha...@oracle.com> wrote: -Xlog:gc+heap=3Dinfo gives you the following kind of output:Unrecognized option: -Xlog:gc+heap=3Dinfo <= div>Must be s

Re: PRT memory usage

2017-08-21 Thread Milan Mimica
Hello Thomas pon, 21. kol 2017. u 18:42 Thomas Schatzl napisao je: > > need you to confirm. Given region size of 8M and default G1 settings: > > * max number of PRT instances is 2^12 for each HR > > Where did you get the 2^12 from? > A bit simplified calculation of OtherRegionsTable::_max_fine_

Re: PRT memory usage

2017-08-21 Thread Thomas Schatzl
Hi, On Sun, 2017-08-20 at 08:57 +, Milan Mimica wrote: > Hello > > I'm (still) trying to figure our high memory usage by PRT. I have > studied heapRegionRemSet.cpp code and came up with a calculation I > need you to confirm. Given region size of 8M and default G1 settings: > * max number of P