Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
H
hivemind
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • hive
  • hivemind
  • Issues
  • #133

Closed
Open
Opened Jan 15, 2021 by Andrzej Lisak@ABWDeveloper

Remove active_votes from post data across bridge and condenser_api

Almost every call in bridge and condenser_api that returns posts includes active_votes. For calls related to popular posts, especially hot and trending, data about votes can take even 90% of whole result (and the same percentage of response time). That data is mostly unused, needlessly eating bandwidth and server CPU. Even the hiveblocks.com that shows all the vote details, it does so only after user clicks on the link - a moment when frontend should ask for votes in separate call. As far as I can see the only information about votes displayed directly with posts is their amount. That information can easily be provided instead of full vote details.

Note that for hivemind prior to HF24 it kind of made sense to include vote details in posts. It was because votes were stored as part of post in large string that needed to be parsed in order to compute data such as number of votes, number of upvotes, cumulative rshares etc. Since hivemind had to decompose vote string in order to supplement data about the post anyway, it was natural to include vote details in the same result. It is no longer true for current hivemind. Now everything related to pulling and processing active_votes is waste.

Edited Jan 15, 2021 by Andrzej Lisak
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: hive/hivemind#133