Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,531
    • Issues 46,531
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,507
    • Merge requests 1,507
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #276188
Closed
Open
Issue created Nov 03, 2020 by Nikola Milojevic@nmilojevic1🔴Maintainer

Enable QueryCache for LoadBalancing

While working on epic: &3873 (closed), I encountered that all GET requests that hit LoadBalancer, are not cached. https://gitlab.slack.com/archives/CMMF8TKR9/p1604072634340600

  • With Load Balancer: Screenshot_at_Oct_26_16-37-18
  • Without Load Balancer: Screenshot_at_Oct_26_15-55-13

We use LB for GET requests unless write happens, otherwise, we use primary. So, we might dynamically switch from LB to direct access, and it looks that when we hit LB, those queries are not CACHED (Caching is disabled)

We can see that for the same end-point, we have: 2 times ~1,256 (1,184 CACHED) executed queries 8 times ~1,256 (0 CACHED) executed queries https://log.gprd.gitlab.net/goto/3202017cc2078fcfab6c0e349d280b7b Screenshot_at_Nov_03_12-37-57

Based on this, it seems that we never enable_query_cache for loadbalancing connections

Edited Nov 03, 2020 by Nikola Milojevic
Assignee
Assign to
Time tracking