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

[WordPress Trac]

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

Comment (by SirLouen):

 If I'm not wrong, you can edit this limit, so this 100-upper limit is just
 the default option. I don't get why 200 or 400 could be more adequate for
 just a random number selected for the sake of querying.

 Replying to [comment:2 desrosj]:
 > I am working internally with a few team members at Bluehost to get some
 memory profiling and data based on our shared hosting configurations to
 help set a better-informed upper bound number.

 I wonder if desroj every got this data.

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