On 2017.04.10 at 13:14 +0100, Richard Earnshaw (lists) wrote:
> On 10/04/17 12:06, Segher Boessenkool wrote:
> > On Mon, Apr 10, 2017 at 12:52:15PM +0200, Markus Trippelsdorf wrote:
> >>> --param ggc-min-heapsize=131072
> >>> 11264.89user 311.88system 24:18.69elapsed 793%CPU (0avgtext+0avgdata
>
On 10/04/17 12:06, Segher Boessenkool wrote:
> On Mon, Apr 10, 2017 at 12:52:15PM +0200, Markus Trippelsdorf wrote:
>>> --param ggc-min-heapsize=131072
>>> 11264.89user 311.88system 24:18.69elapsed 793%CPU (0avgtext+0avgdata
>>> 1265352maxresident)k
>>
>> --param ggc-min-heapsize=262144
>> 10778
On Mon, Apr 10, 2017 at 12:52:15PM +0200, Markus Trippelsdorf wrote:
> > --param ggc-min-heapsize=131072
> > 11264.89user 311.88system 24:18.69elapsed 793%CPU (0avgtext+0avgdata
> > 1265352maxresident)k
>
> --param ggc-min-heapsize=262144
> 10778.52user 336.34system 23:15.71elapsed 796%CPU (0av
On 2017.04.10 at 12:15 +0200, Markus Trippelsdorf wrote:
> On 2017.04.10 at 10:56 +0100, Richard Earnshaw (lists) wrote:
> >
> > What are the numbers with 256M?
>
> Here are the numbers from a 4core/8thread 16GB RAM Skylake machine.
> They look less stellar than the ppc64le ones (variability is s
On 2017.04.10 at 10:56 +0100, Richard Earnshaw (lists) wrote:
> On 09/04/17 21:06, Markus Trippelsdorf wrote:
> > On 2017.04.09 at 21:10 +0200, Markus Trippelsdorf wrote:
> >> On 2017.04.09 at 21:25 +0300, Alexander Monakov wrote:
> >>> On Sun, 9 Apr 2017, Markus Trippelsdorf wrote:
> >>>
> Th
On 09/04/17 21:06, Markus Trippelsdorf wrote:
> On 2017.04.09 at 21:10 +0200, Markus Trippelsdorf wrote:
>> On 2017.04.09 at 21:25 +0300, Alexander Monakov wrote:
>>> On Sun, 9 Apr 2017, Markus Trippelsdorf wrote:
>>>
The minimum size heuristic for the garbage collector's heap, before it
On Sun, Apr 09, 2017 at 10:06:21PM +0200, Markus Trippelsdorf wrote:
> On 2017.04.09 at 21:10 +0200, Markus Trippelsdorf wrote:
> > On 2017.04.09 at 21:25 +0300, Alexander Monakov wrote:
> > > On Sun, 9 Apr 2017, Markus Trippelsdorf wrote:
> > >
> > > > The minimum size heuristic for the garbage c
On 2017.04.09 at 21:10 +0200, Markus Trippelsdorf wrote:
> On 2017.04.09 at 21:25 +0300, Alexander Monakov wrote:
> > On Sun, 9 Apr 2017, Markus Trippelsdorf wrote:
> >
> > > The minimum size heuristic for the garbage collector's heap, before it
> > > starts collecting, was last updated over ten y
On 2017.04.09 at 20:23 +0200, Richard Biener wrote:
> On Sun, Apr 9, 2017 at 4:41 PM, Markus Trippelsdorf
> wrote:
> > The minimum size heuristic for the garbage collector's heap, before it
> > starts collecting, was last updated over ten years ago.
> > It currently has a hard upper limit of 128MB
On 2017.04.09 at 21:25 +0300, Alexander Monakov wrote:
> On Sun, 9 Apr 2017, Markus Trippelsdorf wrote:
>
> > The minimum size heuristic for the garbage collector's heap, before it
> > starts collecting, was last updated over ten years ago.
> > It currently has a hard upper limit of 128MB.
> > Thi
On Sun, 9 Apr 2017, Markus Trippelsdorf wrote:
> The minimum size heuristic for the garbage collector's heap, before it
> starts collecting, was last updated over ten years ago.
> It currently has a hard upper limit of 128MB.
> This is too low for current machines where 8GB of RAM is normal.
> So,
On Sun, Apr 9, 2017 at 4:41 PM, Markus Trippelsdorf
wrote:
> The minimum size heuristic for the garbage collector's heap, before it
> starts collecting, was last updated over ten years ago.
> It currently has a hard upper limit of 128MB.
> This is too low for current machines where 8GB of RAM is n
12 matches
Mail list logo