Bug 116399 - Sending a print job for a 400 paged document is rather slow
Summary: Sending a print job for a 400 paged document is rather slow
Status: RESOLVED DUPLICATE of bug 112989
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: perf
Depends on:
Blocks: Print
  Show dependency treegraph
Reported: 2018-03-14 11:42 UTC by Telesto
Modified: 2019-04-08 05:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Flame Perf Graph for opening Print Dialog (CTRL+P) (57.60 KB, image/png)
2019-04-07 20:32 UTC, Telesto
Flame Perf Graph when giving the print command (78.29 KB, image/png)
2019-04-07 20:49 UTC, Telesto

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2018-03-14 11:42:02 UTC
Sending a print job for a 400 paged document is rather slow

Steps to Reproduce:
1. Open attachment 140185 [details] (bug 116068)
2. Print it to a PDF printer/XPS printer 

Actual Results:  
It takes +/- 90 seconds

Expected Results:
25 seconds

Reproducible: Always

User Profile Reset: No

Additional Info:
Found in
Build ID: 5b87abe06da35ca3a11628674af23460349b439a
CPU threads: 4; OS: Windows 6.3; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-03-12_23:45:38
Locale: nl-NL (nl_NL); Calc: CL

but not in
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Buovjaga 2018-03-15 19:39:18 UTC
Not yet in 5.0.2, but already in 5.3.0 (tested on Win).
I tried bibisection repos on Win, but they acted confusingly: sometimes they did not show any progress in the PDF printing dialog. So I can't say if the problem appeared in 5.1 or 5.2.

Arch Linux 64-bit
Build ID: 28e8c3e28bf4944ecad23961602b9b1f72613d39
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on March 15th 2018
Comment 2 Telesto 2018-03-16 08:37:27 UTC
Might be a dupe (again, great!) of bug 112989.. A the dupes are mine already (keep forgetting about it)
Comment 3 Timur 2018-06-14 12:20:15 UTC
I had 50-55 seconds Export as PDF and Print to PDF in LO 6.2+. Yes, slow. 
It's 15 seconds with 5.2.
As you said, let's close as a dupe if Bug 112989 and check again should that one be resolved. 

You may use Personal Tags to track your own and realted bugs.

*** This bug has been marked as a duplicate of bug 112989 ***
Comment 4 Telesto 2019-04-06 17:25:40 UTC
Slightly opportunistic .. but I would love Noels perf magic in this area ;-). Not sure if it's within his expertise though.. because it's likely - based on bibisect -  Harfbuzz related

-> Opening the Print Preview Dialog -> Slow (not responding)
-> Giving the print job to a virtual printer -> It can nearly see the dialog counts every page

Yes: I'm biased like hell.. I'm the one complaining (I reported this bug and most of the duplicates of bug 112989)

But the performance is quite horrific IMHO. And seems to me everybody would profit There quite something to gain here... IMHO
Comment 5 Telesto 2019-04-07 20:32:30 UTC
Created attachment 150585 [details]
Flame Perf Graph for opening Print Dialog (CTRL+P)
Comment 6 Telesto 2019-04-07 20:49:22 UTC
Created attachment 150586 [details]
Flame Perf Graph when giving the print command
Comment 7 Buovjaga 2019-04-08 05:21:12 UTC
(In reply to Telesto from comment #5)
> Created attachment 150585 [details]
> Flame Perf Graph for opening Print Dialog (CTRL+P)

Looks like you are using ETW for those graphs (perf would be on Linux).

Are you using a master build without debug symbols (you don't mention the version)? Asking because the traces have <itself> at the top and all kinds of "missing". I assume the only way to have one would be to build it yourself with --enable-symbols.

Symbols for release builds should be in the symbol server.

I once tried to get symbols set up with ETW, using UIforETW, but did not succeed. If you manage to get them working, please document the steps in the QA/BugReport/Debug Information wiki page, because ETW is a powerful tool.

I used this blog as a source of information, when I messed around with ETW: