pricingassistant

mrq: Distributed Python Task Queue on Redis and gevent

MRQ is a distributed Python task queue built on MongoDB, Redis, and gevent, designed to handle mixed I/O-bound and CPU-bound jobs. It offers queue management, scheduling, workers, and a dashboard, but has seen no recent maintenance.

View on GitHub Compare
Stars
892
Forks
115
Stars, last 30 days
+1
Last commit
3.4 years ago
Contributors
28

Our take

Inactiveno commits in over a year

Health score

28/100

How it is scored
Activity
19
Community
53
Issues
21
Pull requests
20

+1 stars in the last 30 days

MRQ is a capable, feature-rich queue for Python workloads, but its long period without commits or releases makes adoption a maintenance risk.

Good fit if

  • You already operate MongoDB and Redis and need gevent-based concurrency for Python jobs.
  • You value the included dashboard, per-job logs, and job management controls.
  • You can assess and maintain an inactive project with no recent issue or pull-request activity.

Look elsewhere if

  • You need a queue with recent releases or evidence of ongoing maintenance.
  • Your environment cannot run MongoDB and Redis alongside the workers.
  • You need an actively maintained alternative to compare with RQ or Celery.
All health signals
Last commit2023-06-13 (3.4 years ago)
Commits, last 90 days0
Releases, last 12 months0 (latest 0.9.10, 2018-08-31)
Contributors28 (top contributor: 68% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age12 years

Checked on 2026-10-29 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

893

Forks

114

Change since Nov 16, 2026: 0 stars·0 forks

Overview

MRQ is a distributed task queue for Python, built on MongoDB, Redis, and gevent. It addresses the need to run heterogeneous workloads, from many small I/O-bound tasks to larger CPU-bound jobs, with queueing, worker processes, and concurrent greenlets.

The project aims to pair the simplicity of RQ with performance closer to Celery. Its dashboard provides visibility into jobs and workers, while the command-line tools and Python API let teams enqueue and run tasks.

Key Features

  • Run I/O-bound jobs concurrently in gevent worker greenlets.
  • Split CPU-bound work across UNIX processes, with Supervisord integration.
  • Inspect queued jobs, running workers, and per-task logs in a dashboard.
  • Retry, requeue, or cancel jobs from code or the dashboard.
  • Route jobs to queues and set per-job timeouts and TTL values.
  • Schedule tasks by interval or time of day.
  • Choose sequential or parallel dequeue strategies, including burst mode.

Use Cases

  • A Python backend team can queue outbound HTTP requests or other I/O-heavy work and run them concurrently in workers.
  • A service with both frequent small tasks and occasional larger jobs can route work to queues and scale workers separately.
  • An operations team can inspect job state and logs in the dashboard and manage failed or delayed jobs.
  • A team running periodic maintenance tasks can use the built-in scheduler rather than enqueueing each run manually.

What you need

Detected in the repository

  • Python (from setup.py)
  • A Dockerfile, so it can run in a container
  • A test suite

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install MRQ with pip install mrq, and provide Redis and MongoDB services. See the README for the task, worker, and dashboard walkthrough.

Alternatives

  • dramatiq: Dramatiq distributes Python background jobs through RabbitMQ or Redis, while MRQ uses MongoDB, Redis, and gevent and includes scheduling and a dashboard.
ProjectLanguageLicenseStarsStatus
mrqPythonMIT892Inactive
dramatiqPythonLGPL-3.05.3kActive

Considerations

The project is marked inactive, with no commits in over a year and no releases in the past year. No recent issues were closed or pull requests merged, so teams should expect to take responsibility for compatibility fixes and maintenance. The README describes testing, including worker-interruption and Redis-failure cases, but the supplied project facts indicate no configured CI. Running MRQ also requires both Redis and MongoDB.

Found this useful?

Share it with someone who would like mrq.

Comparisons