Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bridge_api response size #251

Open
roadscape opened this issue Sep 24, 2019 · 0 comments
Open

bridge_api response size #251

roadscape opened this issue Sep 24, 2019 · 0 comments
Labels
communities
Milestone
communities MVP

Comments

@roadscape
Copy link
Contributor

roadscape commented Sep 24, 2019 •
edited
Loading

Check common calls and their response sizes. Identify if there are any low-impact methods to make responses smaller in size.

Currently, /trending is approx 1,150,961 bytes:

  • 74% votes
  • 19% body
  • 5% json

Potential changes:

  • post lists to truncate body (serve preview instead of body)
  • truncate active_votes down to 5 if no observer
  • do not serve json_metadata unless root comment in thread
  • do not serve root_title, etc unless root comment in thread
@roadscape roadscape added this to the communities MVP milestone Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
communities
Projects
None yet
Milestone
communities MVP
Development

No branches or pull requests
1 participant
@roadscape