Bump occurrences page size #1013
Open
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for antenna-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
mihow
approved these changes
Oct 30, 2025
Collaborator
mihow
left a comment
mihow
left a comment
There was a problem hiding this comment.
I a bit hesitant to merge this until we speed up the occurrences API response. Maybe give it one more day and I will try to do that!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
We have talked about bumping the occurrence page size (for example this was suggested by Maxim on a feedback session in Panama). The page size is currently set to 20, however larger pages will also take longer to load, so we need to find a balance.
Quick load time experiment:
In the screenshots below, you can see what takes time is mostly waiting for the server, but also loading content.
I suggest we start updating to 50 and when we can improve the server response time in future, we could try 100?
Screenshots from testing