Re: callgrind metrics was: Re: minutes of ESC call ...

Good question, Matúš

I have been thinking about that also, and was thinking of asking the
qa people for a list of file load/save complaints from fdo.

The test ods should definitely have a graph in it. That is always a
speed bottleneck in Calc. Unfortunately some of the interpretation of
the graph data is deferred now until the user clicks the graph. That
means that some of the biggest loading bottleneck will not be measured
by loperf.

The idea was once to have loperf produce a single perfomance
indicator, and present that as a graph somewhere of the performance
over time. Only retain the underlying data for a short time for dev's
interested in the causes of performance regressions.

Greetings,

Stephan

2013/12/6 Matúš Kukan <matus.kukan@gmail.com>:
> On Thu, 2013-12-05 at 17:23 +0000, Michael Meeks wrote:
> > * Pending Action Items:
> >     + actually produce callgrind performance metrics from VM (Matus)
>
> So - it's running and producing callgrind profiles - Is it possible
> somebody would be interested in them ? They are deleted after 10 days,
> so that should be enough in that case I hope.
>
> And the result (attached) is something like:
> <date> <git-commit> <CEst-for-file1> <CEst-for-file2> ..
>
> What files should it test ?
> Currently it's empty.ods, empty.odt, and sample.xlsx - just some numbers
> in there.
> There can't be too many files nor big ones,  otherwise it takes too much
> time.
>
> Any ideas how to make this useful for you ?
> Btw. it's in buildbot.git/loperf
>
> Where should I upload this history.csv ?
> Post to the list once in a week, or..?
>
> Thanks,
> Matus
>
> _______________________________________________
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libreoffice