Leaderboard, RG fetching data optimization

Questions
1

I have a leaderboard page where most of the workload is coming from fetching data “Seach for Player Points”

SearchPlayerPointsV2
SearchPlayerPointsV2993×599 63 KB

Here is the Player Points Table

SearchPlayerTable
SearchPlayerTable816×679 148 KB

I was curious if it’s possible to optimize this and cutdown on workload?

Currently the Repeating Group shows all Players on the leaderboard which could be a little over 200 players probably each time the page loads.

My initial thought is to “set fixed number of rows” in the RG to something like 10 and have a next button to show the next 10 but would this cutdown on fetching data?

Another thought would be to not show data for those who have zero points?

Im not sure how to do either of these but do you think they would help and would you have any other ideas that may help to bring down the Workload Activity for Fecthing Data from the Search

Any help would be greatly appreciated!

2

You can uncheck “Show all items immediately”

3

Great, I appreciate the response, what will this do to it to help?

4

It won’t load all of the data at once, which will save you on WU. You can use Pagination or further filtering to give the user control over what data to show, and the pagination prevents it from loading all the data at once, a major savings in WU.

This is indeed Pagination and would help!

5

Great Thank you very much! Ive implemented it!

1 Like