rq-scheduler
A lightweight library that adds job scheduling capabilities to RQ (Redis Queue) (by rq)
rq
Simple job queues for Python (by rq)
| rq-scheduler | rq | |
|---|---|---|
| 4 | 27 | |
| 1,387 | 9,518 | |
| 0.5% | 0.7% | |
| 2.2 | 8.3 | |
| about 2 months ago | 11 days ago | |
| Python | Python | |
| MIT License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rq-scheduler
Posts with mentions or reviews of rq-scheduler.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-24.
- Keep the Monolith, but Split the Workloads
-
RQ-Scheduler for tasks in far future?
RQ-Scheduler is another simpler alternative (rq/rq-scheduler: A lightweight library that adds job scheduling capabilities to RQ (Redis Queue) (github.com)) that appears to be good for such purposes. It's not immediately clear if it would suffer from the same issues, but it seems not (Redis manages issues with data loss well, a separate queue is used for the scheduled tasks, etc.). Is anyone aware of any drawbacks to using RQ-Scheduler for something like this?
- Need direction on how to add asynchronous / scheduled tasks on my flask app running on aws beanstalk
-
Some advice: will my setup be production ready?
Some thoughts: - Storing API keys in Redis with AOF and RDB persistence turned on is going to be way faster than storing those keys in Mongo. - Did you mean RQ (redis-queue)/django-rq? If so, it works well as long as you don't need a scheduler for cron-like tasks, which it doesn't include. You can add rq-scheduler for that though: https://github.com/rq/rq-scheduler - Make sure your redis instance has a password -- redis 6 supports ACLs as well - The problem with slow requests is that they tie up app server processes and usually also database connections. That may be fine with a small number of consumers, but if you point your web site at this API, you may run into problems. Consider that if an app server serving web site traffic is waiting for a slow request to your API, then both app servers are affected -- you're now holding resources on the web site and the API, effectively. - HTTP clients often use a default timeout value for requests, and it's a best practice to use such a timeout -- so you'll need to coach your partners consuming this API not to use timeouts for your API.
rq
Posts with mentions or reviews of rq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-14.
-
Redis Re-Implemented with SQLite
That's pretty cool. Reckon it would work with existing code that calls Redis over the wire for RQ?
https://python-rq.org -
The Many Problems with Celery
https://github.com/rq/rq is to the rescue.
-
Keep the Monolith, but Split the Workloads
We use RQ[0], it has Redis as a dependency. It’s pretty straightforward and we’re very happy with it. If you are using Django you may want to look at Django RQ[1] as well. RQ has built in scheduling capabilities these days, but historically it did not so we used (and still use) RQ Scheduler[2] which I think still has some advantages over the built in stuff.
[0] https://python-rq.org/
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
Also had a similar experience using RabbitMQ with Django+Celery. Extremely complicated and workers/queues would just stop for no reason.
Moved to Python-RQ [1] + Redis and been rock solid for years now.
[1] https://python-rq.org/
- Ask HN: Redis Queue Hacks and Questions
- What libraries do you use the most alongside django?
-
Recommendations other than celery to send an API processing in background, which would only take 5 mins to process and API usage would be once a month or so.
Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq
-
GPU instance crashes when two python processes use the same pt file
We have a GPU (G5) instance that uses Python RQ (https://python-rq.org/).
- Dynamically update periodic tasks in Celery and Django
- Celery + RabbitMQ alternatives
What are some alternatives?
When comparing rq-scheduler and rq you can also consider the following projects:
fastapi-cloud-tasks - GCP's Cloud Tasks + Cloud Scheduler + FastAPI = Partial replacement for celery.
celery - Distributed Task Queue (development branch)
django-rq - A simple app that provides django integration for RQ (Redis Queue)
huey - a little task queue for python
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Flask-RQ2 - A Flask extension for RQ.
mrq - Mr. Queue - A distributed worker task queue in Python using Redis & gevent
django-rq - A simple app that provides django integration for RQ (Redis Queue) [Moved to: https://github.com/rq/django-rq]
procrastinate - PostgreSQL-based Task Queue for Python
supervisor - Supervisor process control system for Unix (supervisord)
Apache Kafka - Mirror of Apache Kafka