Hi Michael,
Appreciate your feedback.
I ran callgrind but no output on screen and 0 bytes files generated. I can run it on non-LO exe.
I'll compile LO with --enable-debug and see if situation improves. Please advise if other steps
might be needed.
What's your hunch about how long it should take to update 60K cells with {getCellByPosition(ii,jj)
and setValue() } ?
Moving from interprocess bridge speeded it up for me and I might have given up on further speed-up
too quickly. I can certainly use further speedup.
Thanks
Neeraj
-----Original Message-----
From: Michael Meeks [mailto:michael.meeks@suse.com]
Sent: Thursday, January 10, 2013 4:45 AM
To: Rai, Neeraj [ICG-MKTS]
Cc: 'libreoffice@lists.freedesktop.org'
Subject: RE: [libreoffice-dev] - questions about calc extension
On Wed, 2013-01-09 at 23:18 +0000, Rai, Neeraj wrote:
I looked a little more into your code and copied the getactiveSheet function. Now it takes 12s. I
am happy.
Sorry for the spam - you have good code sitting there.
12s sounds like a long time to me ;-> If you can run your macro under
callgrind:
export OOO_DISABLE_RECOVERY=1
valgrind --tool=callgrind --simulate-cache=yes \
--dump-instr=yes ./soffice.bin -writer --splash-pipe=0
(needs write-permission to the installed libreoffice directory to drop
it's callgrind.12345.txt file)
Then perhaps kcachegrind will show you something interesting for your
use-case.
HTH,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.