Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #802

Closed
Open
Created May 09, 2012 by Administrator@rootOwner

Merge request diffs serialization is a major slowdown

Created by: CedricGatay

I recently had a problem with resque jobs eatings CPU like hell and seems stuck. I digged into the code and found out that the serialization of st_diffs in merge_requests.rb seems to be the major slowdown. In my different attempts, it appears that when I have a lot of diff objects it runs infinitely (361 in the current case).

I can fix try to fix this but I would like some advice on it:

  • is it really necessary to save st_diffs in the database ?
  • if it is, can we try backing it up using JSON instead of the serialize method of ActiveRecord ?

Thanks for the reply

Assignee
Assign to
Time tracking