rrqueue
rrqueue copied to clipboard
traitecoevo
R + Redis queues
Work needed inside of `prepare_expression` only. Major headache is to work out any functions that will likely not be available on the workers. `globals::globalsOf` is likely to be useful in...
To simulate, try with toxiproxy 1. Install `toxiproxy` from [here](https://github.com/Shopify/toxiproxy/releases/latest) and run the server 2. Install `toxiproxyr` with `devtools::install_github("richfitz/toxiproxyr")` 3. In `rrqueue/tests/testthat` run: ``` r ## Attempts at running rrqueue...
This formalises the idea of a "group" of tasks a little. Because tasks write into a "complete" key when they're done (enqueue_bulk / rrqlapply) it might be useful to ask...
This would save on roundtrip communication and might not be _that_ hard to implement. Main issues will be the back and forth with the id counter which is specially allocated.
Not exposed at the moment. There's a fairly high level `monitor` and some lower level ones.
Can we direct stdout to a redis key? Can we arrange for loggr to go to a key (even via an option?)
Will be useful in a cloud environment where the redis server hasn't come up yet. Perhaps set default retries to zero but run with retries on the command line.
Really large objects will just gum up Redis. In some projects we store the filename but not the data; it'd be nice to automate this. This could be done at...