[wp-trac] [WordPress Trac] #45140: REST API: Increase upper bound allowed on per_page argument

WordPress Trac noreply at wordpress.org
Wed Oct 31 05:07:24 UTC 2018

#45140: REST API: Increase upper bound allowed on per_page argument
 Reporter:  danielbachhuber               |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  5.0
Component:  REST API                      |     Version:
 Severity:  normal                        |  Resolution:
 Keywords:  needs-patch needs-unit-tests  |     Focuses:  rest-api,
                                          |  performance

Comment (by dd32):

 > Before we pick per_page=200 vs. per_page=300 vs. per_page=400, we

 I think an important part of this is also to look at each end-point

 For example, requesting 10,000 terms at once might be viable, but the same
 for posts not so much.

 It's going to be the edge-cases on the 0.001% of sites which will cause
 problems, those with hard upper 32M of memory and posts which are 1M of
 text each, etc.  It may even be that we might need to set it at `max 999`
 and have the client back-off and try again at `200` if the response isn't
 valid, etc.

 Is there perhaps a smaller set of endpoints which we can focus on? Terms?
 Posts? Which paginated endpoints affect Gutenberg the most? Which
 endpoints is Gutenberg NOT handling the pagination for well? etc.

Ticket URL: <https://core.trac.wordpress.org/ticket/45140#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list