On Thursday 22 of September 2011, Kohei Yoshida wrote:
> On Thu, 2011-09-22 at 17:09 +0100, Caolán McNamara wrote:
> > Seems to spend all its time getting and setting optimal row
> > heights/widths or something like that in ods/xlsx mode.
>
> Yes. That's an infamous bottleneck. Calc's row height
On Thu, 2011-09-22 at 17:09 +0100, Caolán McNamara wrote:
> On Wed, 2011-09-21 at 11:28 +0100, Michael Meeks wrote:
> > It'd be really interesting to get a callgrind trace of ods / xlsx loading.
>
> oh, as an aside, this is easy to get with
> cd sc
> export VALGRIND=callgrind
> make -sr
>
> Here
On 21.09.2011 13:08, Lubos Lunak wrote:
> On Wednesday 21 of September 2011, Michael Meeks wrote:
>> On Wed, 2011-09-21 at 09:50 +0100, Caolán McNamara wrote:
>>> In an ideal world I imagine the best spent effort would be on improving
>>> the import speed for .ods and .xlsx, seeing as that improves
On Wed, 2011-09-21 at 11:28 +0100, Michael Meeks wrote:
> It'd be really interesting to get a callgrind trace of ods / xlsx loading.
oh, as an aside, this is easy to get with
cd sc
export VALGRIND=callgrind
make -sr
Here's mine FWIW http://www.skynet.ie/~caolan/pub/tmp/callgrind.out.4171
Seems
On Wed, 2011-09-21 at 11:28 +0100, Michael Meeks wrote:
> On Wed, 2011-09-21 at 09:50 +0100, Caolán McNamara wrote:
> > So I've now added a timer listener to our cppunit launcher to tell us
> > how long each test takes[1] and indeed it takes about 70ms to load a
> > .xls, 370ms for an equivalent .o
On Wednesday 21 of September 2011, Michael Meeks wrote:
> On Wed, 2011-09-21 at 09:50 +0100, Caolán McNamara wrote:
> > In an ideal world I imagine the best spent effort would be on improving
> > the import speed for .ods and .xlsx, seeing as that improves the
> > real-world case too.
>
> Agr
Hello Caolan, Michael,
2011/9/21 Michael Meeks
>
> On Wed, 2011-09-21 at 09:50 +0100, Caolán McNamara wrote:
> > So I've now added a timer listener to our cppunit launcher to tell us
> > how long each test takes[1] and indeed it takes about 70ms to load a
> > .xls, 370ms for an equivalent .ods a
On Wed, 2011-09-21 at 09:50 +0100, Caolán McNamara wrote:
> So I've now added a timer listener to our cppunit launcher to tell us
> how long each test takes[1] and indeed it takes about 70ms to load a
> .xls, 370ms for an equivalent .ods and about 500ms(?!) for an
> equivalent .xlsx
Ooh :
On Tue, 2011-09-20 at 11:27 +0200, Markus Mohrhard wrote:
> The sc unit tests are slow because we use the filter-tests as an way
> to test not only the import but also the first recalculation. We
> havenow already about 10 files that we import and check and I have
> some additional that are not yet
