react-page-navigator - Performance on large page library

[lfokke]

Disclaimer

Yes

Sample

react-page-navigator

Contributor(s)

@aakashbhardwaj619

What happened?

Hi,
We've been using v1.7 on a large page library (2000+ pages) without any issue.
some time ago we moved to v1.10 (because of the Sticky mode) and since then, performance is poor on this large library. When deployed on a small library, performance is great.
I discovered that this is due to a change in the way the page content is loaded. In 1.7 it's directly with the page ID but now it's a query on the URL.
It looks like this query causes the increased load time (I saw this with the devoper tool in Edge).

Can you think of a solution for this? For now we've reverted back to 1.7 but the Sticky mode is very much missed.

Steps to reproduce

1.Create a large page library ;-)
2.Place the webpart on a page
3.Wait some 60 or 90 seconds

Expected behavior

quick response

Target SharePoint environment

SharePoint Online

Developer environment

None

Browsers

• Internet Explorer
• Microsoft Edge
• Google Chrome
• FireFox
• Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

What version of Node.js is currently installed on your workstation?

v18.18.2

What version of Node.js is required by the sample?

v18

Paste the results of SPFx doctor

n.a.

Additional environment details

No response

[github-actions]

This issue has been marked as stale due to no progress in over 90 days. If you are still experiencing this issue, please provide additional information so we can help you resolve it.

[lfokke]

No change here.... still waiting for a solution