G1: higher perm gen footprint or a possible perm gen leak?

[Wolfgang Pedot]

Hi,

 >> I dont really think G1 causes this 3-1 rythm specifically but whats
>> interesting is that CMS with ClassUnloading never got significantly
>> below that 0.8GB if I remember correctly.
> Try
>
> -XX:MarkSweepAlwaysCompactCount=1
>
> which should make every full GC compact out all
> the dead space.
>
> Alternatively try
>
> -XX:MarkSweepAlwaysCompactCount=8
>
> and see if that changes the pattern.
>

thats it, with a value of 1 all PermGen collects reach the same usage.
Since the compacting collects are not visibly slower than "normal" full 
GCs I guess I´ll lower that value on the live system to increase time 
between full GCs.

thanks for the tip
Wolfgang