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-01 UTC."],[[["This webpage provides a version history and documentation for `structgoogle::cloud::storage::MaxResults`, ranging from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["Each version listed links to its corresponding documentation for `structgoogle::cloud::storage::MaxResults`, allowing users to access specific details for that version."],["The documentation highlights that `MaxResults` is used to limit the number of results per page when listing Buckets and Objects, with the goal of reducing the memory needed by the Bucket and Object iterators."],["Using smaller page sizes can reduce memory, but it may require more requests to iterate through all Buckets or Objects, according to the documentation."],["The documentation includes a function, `static well_known_parameter_name()`, which returns a constant character pointer but has no further description."]]],[]]
