Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P PyAV
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PyAV
  • PyAV
  • Issues
  • #166
Closed
Open
Issue created Apr 13, 2016 by Mike Boers@mikeboers

Logging is very slow

During #128 (closed) and #164 (closed), the actual decoding takes ~6 seconds. Processing the main log callback adds very little overhead. Getting to the point of being ready to dump into the Python logging system adds ~2s. Actually doing it adds another ~4s. So that is fully an additional 100% for logging the same message thousands of times.

Perhaps we should severely raise the default logging threshold to ERROR.

It would be interesting to see if we could instrument the loggers so that the C callback is aware of the minimum Python threshold.

Assignee
Assign to
Time tracking