media library doesn't handle many BrowseMedia children well

[bushvin]

When creating the BrowseMedia Object to display the contents of a particular media_content_id, return time increases when having many (50+) children to display.

Before trying to build something for a platform I'm working on, is there anything in the makes to provide automatic pagination of a big list of children? ie 1000+

I've tested reaction times by creating loops without actually fetching info, which points me to believe the issue is somewhere in the exchange of the backend to the frontend, or the frontend itself.