Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos-analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos-analysis
  • Issues
  • #9

Closed
Open
Created May 18, 2020 by Mykhailo Dalchenko@mdalchen

Setup efficient unpacker logging

Summary

Unpacker uses built-in python logger module. While this module is very handy in setting up different levels of verbosity and support different handlers (console, file etc.), it comes with a significant overhead even for silenced calls (i.e. if one has multiple debug statements in the code, parsing them may slow down the code very significantly even when logging level is set to info).

What is the expected correct behavior?

Need to provide proper console and file handlers for logger and optimize log calls. Pehaps provide logging functionality on per-event basis to reduce the number of logger.debug statements.

Relevant logs and/or screenshots

Assignee
Assign to
Time tracking