mrq vs rq

Python background job queues compared

mrq and rq both queue Python jobs for workers to process outside an application’s main flow. mrq combines Redis, MongoDB, and gevent, with tools for mixed I/O-bound and CPU-bound work; rq uses Redis or Valkey and emphasizes a straightforward queueing model with scheduling and retries.

mrqrq
LanguagePythonPython
LicenseMIT—
Stars89210.7k
Forks1151.5k
Last analyzedOct 29, 2026Nov 6, 2026

Key differences

  • mrq uses both Redis and MongoDB, while rq uses Redis or Valkey.
  • mrq supports concurrent gevent greenlets for I/O-bound work and UNIX processes for CPU-bound work; rq offers worker types with different tradeoffs in isolation and overhead.
  • mrq includes a dashboard for inspecting jobs, workers, and task logs; rq’s listed features include webhooks, recurring jobs, and controls to limit duplicate or concurrent jobs.
  • mrq is marked inactive, with no commits in over a year; rq is described as active, with recent commits and releases.
  • mrq has an MIT license, while rq’s repository license metadata is marked NOASSERTION.
  • mrq has 892 stars and 115 forks, while rq has 10.7k stars and 1.5k forks.

Choose mrq if you…

  • need gevent concurrency for I/O-bound tasks alongside process-based CPU work.
  • want a dashboard to inspect jobs, workers, and task logs.
  • need queueing and scheduling features and can take responsibility for maintenance.
Read the mrq analysis →

Choose rq if you…

  • want to use Redis or Valkey without adding MongoDB as a dependency.
  • need recurring jobs with cron rules, retries, webhooks, or duplicate-enqueue controls.
  • prefer a project described as active, and can review its license terms and serializer security considerations.
Read the rq analysis →

Compare the numbers side by side, or add more projects

This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.