On Monday, March 22, 2021 9:01:21 AM CET Dag wrote: > Hi, opened the odf spec in words the other day. > This is a document with 800+ pages and a TOC of 60+ pages. > I did the same in LO to compare. > Don't take the absolute times too seriously as my box is well into its > teenage years. > But, I think comparison with LO says a lot: > > Open: 2,5 mins, LO: 40 secs. > Except that TOC page numers is not shown (just ###), navigation, scrolling > etc works fine. > Save: 4 mins, LO: 30 secs. > > And now to the bad part: > When a try to type a character words freezes for about 50 secs. > It seems the whole doc is re-layouted and also the TOC is updated (page > numbers appear). > > Then when auto-save kicks in words freezes again without any feedback. I > expected to see a status meassage and a progress bar, but no. > > Krita solved freeze by making a copy of the doc and save in the background. > > LO is better (but not good). > Generally you can type new text wo problems but it freezes for shorter > periods (maybe when updating page numbers), and it freezes when > auto-saving. > > It never updates the TOC, this needs to be done manually. > > Suggestions (just my 2 cents): > 1) TOC should be updated manually to avoid re-layout. > 2) Auto-save in the background. > 3) Minimize re-layout by e.g. only re-layout dirty pages before and > including the displayed page(s).
Hi Thanks for bringing this topic back on the table, long time I did not try to do that. On my computer, opening with LO takes 4s, 20s with words… so about the same ratio as you have. Since my last experiment in this topic, the performance analysis tooling has improved so much that this will be a fun thing to do. I'll see what this gives. And I completely agree with at least parts 1 and 3 of your conclusion. Can not tell for the second part, I must think a bit more about it. And I disagree with René's conclusions. Having performance issue today doesn't mean we can not fix them. And unlike the webbrowser comparison, we are not chasing a perpetually moving target with thousands of corporate developers adding features on their engines while being 0.1 unpaid developer on our engine… It's more like a few unpaid developers against less unpaid developers. Still not the best position for us, but far more manageable. Pierre
signature.asc
Description: This is a digitally signed message part.
