<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Substantial performance deterioration by scroll through cells via macro in LibreOffice Calc"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=78254#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Substantial performance deterioration by scroll through cells via macro in LibreOffice Calc"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=78254">bug 78254</a>
from <span class="vcard"><a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> <span class="fn">Michael Meeks</span></a>
</span></b>
<pre>Priority-wise, the real question is if any hackers want to spend more time
trying to fix it =) there is no real way to encourage volunteers to do that by
prioritizing it differently. The best way to affect change here is to eg. add
some SAL_DEBUGs in the code there to print out what is going on, and/or try to
work out what is going on - why do we adjust the heights here ? do we do that
repeatedly ? what rows are being measured ? is there some way of significantly
optimizing this by looking at spans instead of individual rows etc. etc. anyone
can do that work - if almost any semi-technical person can spend a few days on
it they should make progress. Getting a good bisection would also help. Noel's
commit description doesn't seem to match the callgrind trace.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>