819-pages ODT attachment 121138 [details] from bug 96337 and bug 129529 is slower to open in LO than OO.
TBD where slowness/regression started and if there's a dump.
Note:can be tested up to 6.1 and again from 6.4.2 and 7.0+.
Build ID: d7cab304e7dd22fd12443a1ee3b6a9c463bf9a3d
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default;
Locale: ca-ES (ca_ES.UTF-8)
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Version 126.96.36.199.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
@Timur, why is it tagged as a regression ?
My experience in Windows is that OO 3.3 took less to open compared to LO 6.1 where worked before (0:28 to 0:58 on my slow system).
I'm waiting master Windows build to retest.
@Xisco: I don't know why you confirmed so I set back Unconfirmed. Linux difference is rather small 4.1 vs. 7.0+. Please also test OO.
(In reply to Timur from comment #5)
> @Xisco: I don't know why you confirmed so I set back Unconfirmed. Linux
> difference is rather small 4.1 vs. 7.0+. Please also test OO.
I confirmed it because there a performance issue anyway, either it's a regression or not...
I got a freeze when tried open the file in
Версия: 188.8.131.52.alpha0+ (x64)
ID сборки: cf96cb11e2a46c452a273ded1c66c556118983cf
Потоков ЦП: 4; ОС: Windows 10.0 Build 17763; Отрисовка ИП: GL; VCL: win;
Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU
Linux same system
7.0+ master (freeze on use!):
6.4 master (updated for backport)
6.3 master (with fix for fileopen): bibisect not updated for backport, Xisco please do
6.2 master: cannot open because of bug 129529
5.2 master (5.2. oldest gives an error):
There's continuous slowing down. So not sure if bibisect is possible.
Biggest issue now is freeze in 7.0+ with freeze on use: scroll beginning-bottom 3 times. I don't see it in 6.4+.
Xisco, can this be bibisected in 7.0+ if older couldn't be open?
I don't see freeze now in Windows. I bibisected it:
For Roman's source, bibisect commit is eae8f3cfc609556df2ee5111225db1fd45ef2361.
Current bibisect master source is 017f90788c330d2e35a9c05a56b564d0ab4aafaf and bibisect is 63a56e5ec52906ba382acdeef4b48f83e5335a88.
1988b3c2e0dc93b2e3e96d2af99e95c2078fbfa7 is the first *good* commit
Date: Tue Mar 24 21:08:08 2020 +0100
Previous source sha:7dcf08fe6f14951cdf752a3772f25297cc238ce3. Singe commit.
commit 642cdf2d8341f0b202f01718ccb63ac1b976e18e [log]
author Jan-Marek Glogowski <email@example.com> Tue Mar 24 18:59:22 2020 +0100
committer Jan-Marek Glogowski <firstname.lastname@example.org> Tue Mar 24 21:00:57 2020 +0100
parent 7dcf08fe6f14951cdf752a3772f25297cc238ce3 [diff]
tdf# bug 131530 keep prepending footnote frame
I experienced another crash few times, when I scrolled immediately on open, without waiting for repagination.
That's likely different but not reproducible each time.
Linux 7.0+ master:
We are now back at the bug report. Looks like there's some slowing down.
But I don't think perf bibisect is possible. Maybe flamegraph would help.
(In reply to Timur from comment #11)
> I experienced another crash few times, when I scrolled immediately on open,
> without waiting for repagination.
> That's likely different but not reproducible each time.
Hmm, have seen that too.. (not for this doc)
Created attachment 160680 [details]
Here's a Flamegraph retrieved on pc Debian x86-64 with master sources updated today.
Xisco, please comment. What can be done with flamegraph, now that Julien was kind to get it?
16 seconds for me
Version: 184.108.40.206.alpha0+ (x86)
Build ID: 9af38b4504ccda57a0c32eb8bdd03e5a8ca29ddc
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
(In reply to Telesto from comment #16)
> 16 seconds for me
> Version: 220.127.116.11.alpha0+ (x86)
We have different systems so best to compare this with older LO open time on the same machine, like in Comment 8. There is TimeMem for Windows.
Perhaps more Linux than Windows.. there is annoying idle process spending lots of time layouting the footnotes..
File opening as such.. not really an issue
Build ID: c344de1b9985b6ca10b354e24151d0bdf92dc20e
CPU threads: 2; OS: Linux 5.3; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US
File is certainly slower compared to Windows, with gen and gtk3 backend. Pages being filled after scrolling through