Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,223
    • Merge requests 1,223
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #299540

Closed
Open
Created Jan 22, 2021 by Eugenia Grieff@egrieffDeveloper

Cache epics count in group pages sidebar

Related to #243753 (closed)

Similar to the implementation for issues, we could save page load time for all pages at a group level, by caching the epics count in the sidebar.

The query for this count is performed in EE::GroupsHelper and called from the partial epic_link that is then called from the group sidebar partial.

To be determined:

  • Do we also want to cache and round this count only after a certain value? Seems like the number of epics tends to be significantly lower than the number of issues, so if we want to replicate this behavior maybe we want to consider a different threshold.
Edited Jan 22, 2021 by Eugenia Grieff
Assignee
Assign to
Time tracking