pueue VS BeanstalkD

You can probably do a good subset it in bash, it's just a nicer interface with a lot of configurability and several convenience features.

I'm generally a big fan of showing alternatives: https://github.com/Nukesor/pueue/?tab=readme-ov-file#similar...

Would you be willing to write a proper guide on how to do all of these things in bash? It would be great to have this as guide an alternative inside the Pueue wiki and link to it. It'll help people to make a more informed decision on whether they need this tool or not.

there is a command line manager for long running tasks called Pueue. It is released into Nix, Arch, Alpine, Void, etc, but not for Debian based distros. I know that releasing into Debian is a bit more challenging, but I just wanted to ask if anybody here might be interested in packaging it. Just as a disclaimer, I am not the author of this project, just a regular user.

This one? https://github.com/Nukesor/pueue

How about this: https://github.com/Nukesor/pueue/? I have it bookmarked from a thread here from few years back and never got to test it eventually, but maybe it will serve your purposes?

Multiplexing is great for your multiple outputs, but I would highly recommend using pueue & pueued for job control. Lets you organize your background jobs into groups which can be paused, resumed, etc. Also lets you act on jobs from different terminals w/the pueue interface.

pueue -- a queue for tasks, running in background

For the command that takes a long time to complete, I always use pueue to run. This thing let you run multiple commands in order and can schedule the execution later which is really helpful to my workflow.

That said, you're basically building pueue. https://github.com/Nukesor/pueue/blob/main/ARCHITECTURE.md might give you some pointers. From reading it, there seems to be a mishmash of tokio stuff, and then everything gets serialised onto an MPSC channel (that's serviced by TaskHandler, on a single thread that's also responsible for polling for finished processes etc, every 200ms).

exchange for pueue and you can even queue them up.

This is the only one I know of: https://github.com/Nukesor/pueue

There's beanstalkd, it has a few Python libraries and it works out of the box with ActiveJob via Backburner.

https://beanstalkd.github.io/

Messaging/Queueing Systems (Amazon SQS, RabbitMQ, Beanstalkd)

Not when a queue is involved. IME trying to replicate something like beanstalkd (https://beanstalkd.github.io/) in postgres is asking for trouble for anything but trivial workloads.

If you're measuring throughput in jobs/s, use a real work queue.

Before Kafka was a standard, I created a go library for beanstalkd that act like an RPC.

Then there are queue libraries like beanstalkd, RabbitMQ or built-in features like queues from Laravel. These will probably get you quicker to your goal then trying the process managing route.

The only task queue I loved was beanstalkd -- it's beautifully written and highly performant. Starting it takes seconds and it's been running for a decade:

https://beanstalkd.github.io/

It's not rust (it's C), but beanstalkd is a pretty incredible work queue that processes millions of jobs a day (10K+/s at peak) for my company. I know there are a few rust drivers available.