Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bliss bliss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 546
    • Issues 546
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 146
    • Merge requests 146
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • BlissBliss
  • blissbliss
  • Issues
  • #2543
Closed
Open
Issue created Feb 01, 2021 by Matias Guijarro@matias.guijarroOwner

to discuss: remove old scan profiling

Scan profiling does a lot of memory allocations. It is not a problem per se, but now that we have yappi I don't think we should keep the old statistics.

Also, scan profiling is invasive in the code since we have to deal with it ourselves.

Scan.statistics is only useful if someone wants to look at statistics after a scan has been done: but, do we really use it ? Usually when a performance problem is suspected, the scan is run again with yappi.

So, I would recommend to remove it.

Linus made a great job with his profiling tool => I am more in favour of this initiative if we need something more elaborate.

Edited Feb 01, 2021 by Matias Guijarro
Assignee
Assign to
Time tracking