-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathREADME.Rmd
More file actions
49 lines (34 loc) · 1.59 KB
/
README.Rmd
File metadata and controls
49 lines (34 loc) · 1.59 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
---
title: "redisProgress Package"
author: "Clément Turbelin"
output: github_document
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE, comment = "#>")
```
## Overview
The goal of redisProgress is to create a progress bar system to follow tasks distributed across several R instances (on the same host or several). It uses Redis instance to follow tasks progress.
Tasks are grouped in a named "queue" and can be monitored together on the same screen.
## Installation
```R
# Install the released version from CRAN:
install.packages("redisProgress")
# Install the cutting edge development version from GitHub:
# install.packages("devtools")
devtools::install_github("cturbelin/redisProgress")
```
## features
- Register progress about a set of tasks (grouped into a named `queue`), each task can have an arbitrary number of steps.
- Task can log a message to the progress queue
- Queue name can be generated ensuring it's unique (a new queue name will be generated each time the main script is run).
- Progress of tasks of a queue can be followed using `redis_progress_monitor()`.
## Usage
See [introduction vignette](vignettes/introduction.Rmd)
## Redis Client implementations
redisProgress can handle several packages implementing redis client API
- `rredis`
- `RcppRedis`
- `redux`
- `rrlite` (Redis without Redis)
`redis_client()` creates a client object embedding the connection context, using a unified interface, regardless the
redis package used. The connection parameters (host, port,...) will be propagated to the R instances.