You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are already fetching all the results, the button is only to actually show the remaining ones. This is an optimisation to speed up rendering on the client. We could paginate the results, but I'm pretty sure people would be very annoyed if they need to click several times to find a specific result (given that the total number has a practical bound).
Theoretically we would load the remaining results lazily, but we are also sending updated ranking for all the results during realtime update (the payload is generated once and sent to all clients).
But it may be worth investigating load time differences for bigger rounds with lazy loading and make improvements based on that.
Per discussion via video call, lazy loading results is a very hard problem, best left to when there is a clear need for it.
In the meantime, this remains a UX/load speed concern - some sort of UI/UX design where by a user can do the following would be a welcome (but not urgent) contribution:
see the Top 100 results by default
Jump to a certain result and show the ~50 results on either side of (ie, show me number 150) - use case here is to figure out what is needed for advancement to the next round in a large round
"Follow" a certain competitor (the user being the default suggestion) - so that as their results get entered, you see their current position and the ~50 results on either side of it (to monitor how someone is doing as results are entered)
In larger rounds (several hundreds) this is resource-intensive, and causes unnecessary slowdown for the user.
The text was updated successfully, but these errors were encountered: