Hi, we use jpg viewer. page preload count is set to 2 by default.
Viewer loads first 2 pages initially.
Now if user scrolls to say page no. 200, then viewer attempts to load pages from 3 to 200, sequentially, which lead to lot of wait time based on server loads for user to see content of page interested in e.g. 200 in this case.
Can the operation of loading pages be optimized ? one option can be loading pages descending.
e.g. in this case 200 to 3 and in parallel ?
Could you please provide more details about the specific viewer you are using and the environment setup? Additionally, are you looking for a code solution or a configuration change?
Groupdocs viewer for .NET. We use Jpg Viewer. On following version.
<PackageReference Include="GroupDocs.Viewer" Version="24.12.0" />
<PackageReference Include="GroupDocs.Viewer.UI" Version="6.0.30" />
<PackageReference Include="GroupDocs.Viewer.UI.Api.Local.Cache" Version="6.0.5" />
<PackageReference Include="GroupDocs.Viewer.UI.Api.Local.Storage" Version="6.0.4" />
<PackageReference Include="GroupDocs.Viewer.UI.SelfHost.Api" Version="6.0.32" />
<PackageReference Include="GroupDocs.Viewer.UI.Api.AzureBlob.Storage" Version="6.0.6" />
Thank you for sharing the package versions. I’m able to reproduce this issue. We’ll take a look and consider possible improvements. The issue ID is VIEWERNET-5174
1 Like
This improvement was implemented in the latest version of GroupDocs.Viewer.UI package.
This change was introduced only in version 8.x version of package (8.0.3).
When PreloadPages is set to a value greater than 0, the UI loads pages in chunks.
With this change, the UI will skip loading pages that have been scrolled past and will instead load the current page and the N-1 consecutive pages from the point where the user stopped scrolling, where N equals PreloadPages.
This enhancement prevents users from waiting for all previously scrolled pages to load, reducing loading times and improving the user experience.
Please let us know if it works as expected for you.