Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mason-today-web
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SRCT
  • mason-today-web
  • Issues
  • #17

Closed
Open
Created Jul 17, 2018 by Landon DeCoito@rdecoitoMaintainer

Implement multiprocessing

Summary

We currently use the thread module to run a separate thread which continually pings the scheduler to update the database at 2:00 am every day. It's been recommended that we switch away from multi-threading to a more efficient system. Try to do that.

Related links

The currently-used thread module (What we want to get rid of): https://www.tutorialspoint.com/python/python_multithreading.htm

Celery: http://docs.celeryproject.org/en/latest/getting-started/first-steps-with-celery.html

Python multiprocessing module: https://docs.python.org/2/library/multiprocessing.html

Edited Jul 17, 2018 by Landon DeCoito
Assignee
Assign to
Time tracking