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
  • #132

Closed
Open
Opened Jan 13, 2021 by Dan Notestein@danOwner

Code and test performance of a prototype replacement of get_account_history API implemented in hivemind/postgres

This task requires a hivemind database that has been supplemented with the data provided by the new hived plugin that stores block meta data and operations history to a postgres database.

Implementation should be relatively simple, but there's a couple performance metrics to measure: API latency, performance under load conditions, and ability to filter further into the past than was reasonably achievable using the hived API (hopefully, we can remove all limitations on how far back a request of a filtered set of operations can go).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: hive/hivemind#132