The account/egress/get handler first fetches the spaces that the given account owns. It then queries the spacestats table to fetch egress numbers per space. This is done sequentially, so an account that owns a lot of spaces could make the handler slow due to the many queries being run. Parallelizing these queries would allow the handler to be as slow as the slowest query.
Space in memory or serialized to the network shouldn't be an issue below 500 spaces, which gives plenty of room. In any case, adding pagination per N spaces to the account/egress/get capability would be a good solution if this is a concern.