Hey,
On Mon, Sep 28, 2015 at 3:29 PM, Noel Grandin wrote:
>
>
> On 2015-09-28 03:11 PM, Markus Mohrhard wrote:
>
>>
>>
>> I'm not sure if I understand your comment. Can you please clarify what
>> you mean with that? Maybe my understanding of our
>> memory allocators is bad but I see not how this
On 2015-09-28 03:11 PM, Markus Mohrhard wrote:
I'm not sure if I understand your comment. Can you please clarify what you mean
with that? Maybe my understanding of our
memory allocators is bad but I see not how this comment applies to the
discussion.
I'm saying that in general I regard c
Hey,
On Mon, Sep 28, 2015 at 2:13 PM, Noel Grandin wrote:
>
>
> On 2015-09-28 11:11 AM, Markus Mohrhard wrote:
>
>> Hey,
>>
>>
>> So it seems that the system allocator is actually even worse as can be
>> seen at
>> http://perf.libreoffice.org/perf_html/suite_cppu_sc.html
>>
>>
>> I'll leave it i
On 2015-09-28 11:11 AM, Markus Mohrhard wrote:
Hey,
So it seems that the system allocator is actually even worse as can be seen at
http://perf.libreoffice.org/perf_html/suite_cppu_sc.html
I'll leave it in for a bit as I want to see what happens if we increase the
memory for the vm but I fe
Hey,
On Mon, Sep 28, 2015 at 8:25 AM, Markus Mohrhard <
markus.mohrh...@googlemail.com> wrote:
> Hey,
>
> On Sat, Sep 26, 2015 at 11:39 PM, Michael Meeks <
> michael.me...@collabora.com> wrote:
>
>> Hi Markus,
>>
>> On Sat, 2015-09-26 at 20:51 +0200, Markus Mohrhard wrote:
>> > so we have been ru
Hey,
On Sat, Sep 26, 2015 at 11:39 PM, Michael Meeks wrote:
> Hi Markus,
>
> On Sat, 2015-09-26 at 20:51 +0200, Markus Mohrhard wrote:
> > so we have been running our in-build performance tests now for a few
> > weeks and recently discovered that our internal memory allocator is
> > causing spik
Hi Markus,
On Sat, 2015-09-26 at 20:51 +0200, Markus Mohrhard wrote:
> so we have been running our in-build performance tests now for a few
> weeks and recently discovered that our internal memory allocator is
> causing spikes in the runtime.
What fun =) the irony is that it was written t
Hey,
so we have been running our in-build performance tests now for a few weeks
and recently discovered that our internal memory allocator is causing
spikes in the runtime. It became even worse during the weekend with the
tests taking 200 times the instructions. Most of it seems to be spend in
our
