Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • 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 44,289
    • Issues 44,289
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,283
    • Merge requests 1,283
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • #34781
Closed
Open
Issue created Oct 23, 2019 by Kamil Trzciński | OoO 2022.07.23 till 2022.08.20@ayufan🌴Maintainer

Make append of chunks to be performant

Currently when appending chunks over Redis we always read a chunk, add data, and write it.

This is super slow, as reflected on https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/4667#note_206627709.

We should rather make the Redis operation to truncate (up to offset), append, and confirm.

We don't really seem to need to read the chunk to perform append of 3-100 bytes.

Assignee
Assign to
Time tracking