Bug 449448 - Pre-render the subsequent page, and speed-up the large PDF rendering (even the text PDFs are too slow at the moment)
Summary: Pre-render the subsequent page, and speed-up the large PDF rendering (even th...
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-01 08:03 UTC by mikebdp2
Modified: 2022-03-05 04:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mikebdp2 2022-02-01 08:03:41 UTC
I have a 70MB PDF file, which is mostly text. It renders too slow, and I have to wait sometimes almost half minute when I simply switch a page. The near pages should be rendered in advance at background mode to save the time, and in general this should be optimized

Platform: Alpine Linux / PostmarketOS running on a Pinephone with KDE Plasma Mobile
Comment 1 mikebdp2 2022-02-01 08:04:29 UTC
Moving to "general" because this pre-rendering may be related not only to PDFs
Comment 2 Albert Astals Cid 2022-02-01 13:16:05 UTC
Just to be clear, you're speaking about the Okular *mobile* interface and not the desktop one, right?
Comment 3 mikebdp2 2022-02-01 15:38:27 UTC
(In reply to Albert Astals Cid from comment #2)
> Just to be clear, you're speaking about the Okular *mobile* interface and not the desktop one, right?

I am using a Pinephone, which runs a PostmarketOS (https://postmarketos.org/) based on Alpine Linux (https://alpinelinux.org/).
Therefore, I think I use a desktop interface: just constrained by a small screen size and may be affected by lower hardware performance.
Comment 4 Albert Astals Cid 2022-02-01 15:43:10 UTC
Why would PostmarketOS  a mobile OS, use the desktop variant of Okular? Makes no sense to me.

Anyhow, it's easy to solve, can you please attach a screenshot?
Comment 5 mikebdp2 2022-02-01 18:54:16 UTC
(In reply to Albert Astals Cid from comment #4)
> Why would PostmarketOS  a mobile OS, use the desktop variant of Okular?
> Makes no sense to me.

Technically this is a full-featured Linux, and it's possible to use Pinephone as a regular Linux desktop together with a dock adapter.

(In reply to Albert Astals Cid from comment #4)
> Anyhow, it's easy to solve, can you please attach a screenshot?

Here's a screenshot - https://imgur.com/a/kW3jJnW , hope it could help to determine if that's really a desktop or mobile Okular UI
Comment 6 Albert Astals Cid 2022-02-01 19:08:23 UTC
Super weird decision, the desktop UI is not mobile optimized, but whatever, that's out of scope.

I have bad news for you, we already prerender the subsequent page. If it's not happening for you something is broken on your end.

Maybe you chose "low memory usage" on the settings?
Comment 7 mikebdp2 2022-02-01 19:23:10 UTC
(In reply to Albert Astals Cid from comment #6)
> Super weird decision, the desktop UI is not mobile optimized, but whatever,
> that's out of scope.

If by mobile UI, you mean the UI found in Android app: Android apps aren't compatible with Linux (without some emulation). For Linux, there's a desktop Okular. PostmarketOS, like the other Pinephone-compatible distros, provide the mobile UI of an OS itself - i.e. Phosh is "mobile GNOME", Plasma Mobile is a "mobile KDE" - but the apps themselves are the regular desktop Linux apps... Or the Okular mobile UI is available for "desktop Linux" too?

(In reply to Albert Astals Cid from comment #6)
> I have bad news for you, we already prerender the subsequent page. If it's
> not happening for you something is broken on your end.
> 
> Maybe you chose "low memory usage" on the settings?

No, I didn't change any settings
Comment 8 Albert Astals Cid 2022-02-03 22:49:14 UTC
> Or the Okular mobile UI is available for "desktop Linux" too?

Obviously it is, why would I be recommending you to use it otherwise?

> No, I didn't change any settings

Ok, hard to debug for me without access to such a phone, but one thing you could do (assuming you have access to kdebugsettings and a terminal) is this.

Open kdebugsettings, search for okular and change all the options to full debug.

Then start Okular from a terminal and you should see debugs like

org.kde.okular.core: sending request observer=0x55d55f5751d0 1461x1960@377 async == true isTile == false
org.kde.okular.core: sending request observer=0x55d55f5751d0 1461x1960@378 async == true isTile == false
org.kde.okular.core: sending request observer=0x55d55f5751d0 1461x1960@376 async == true isTile == false

This is okular asking for page 377, 378 and 376 to be rendered (i'm on page 377 of that file).

Do you see something like that?
Comment 9 Bug Janitor Service 2022-02-18 04:37:01 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2022-03-05 04:35:50 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!