Limit the number of results per page when listing Buckets and Objects.
Applications may reduce the memory requirements of the Bucket and Object iterators by using smaller page sizes. The downside is that more requests may be needed to iterate over the full range of Buckets and/or Objects.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-02 UTC."],[[["This webpage provides documentation for various versions of the `MaxResults` structure, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["`MaxResults` is used to limit the number of results returned per page when listing Buckets and Objects, which is a parameter that can help reduce memory usage."],["The `well_known_parameter_name()` function is described within the page and it returns a constant character pointer (`char const *`), although the specific description is empty."],["Using smaller page sizes with `MaxResults` can reduce the memory footprint of Bucket and Object iterators, but may increase the total number of requests to retrieve the full range of data."]]],[]]
