Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Enterprise Edition
GitLab Enterprise Edition
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 3,583
    • Issues 3,583
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 207
    • Merge Requests 207
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Enterprise EditionGitLab Enterprise Edition
  • Issues
  • #8091

Closed
Open
Opened Oct 20, 2018 by Olivier Gonzalez@gonzoyumo🚀
  • Report abuse
  • New issue
Report abuse New issue

Improve performance of Security Report storage with bulk insert/upsert

Problem to solve

Security Report storage algorithm currently uses N+1 queries and find_or_create_by calls which is not the most performant approach.

Further details

(Include use cases, benefits, and/or goals)

Proposal

Replace these queries with bulk insert and upsert.

What does success look like, and how can we measure that?

Store Security Reports with ~1 query per table instead of the current N+1 scheme.

Links / references

#6717 (closed)

!7578 (merged)

Edited Oct 20, 2018 by Olivier Gonzalez

Related issues

Assignee
Assign to
Epic
11.11
Milestone
11.11
Assign milestone
Time tracking
None
Due date
No due date
9
Labels
Accepting merge requests GitLab Ultimate Secure backend database devops:secure feature performance sast
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ee#8091