redisSetPipeline: Set the Redis message blocking state.

Description Usage Arguments Details Value Note Author(s) See Also Examples

View source: R/controlCMD.R

Description

Use redisSetBlocking to set the rredis client to blocking (default) or non-blocking Redis communication mode.

Usage

1
2

Arguments

value

TRUE indicates Redis pipelined mode, FALSE non-pipelined mode. Just to be extra confusing, it's the opposite for the older, now deprecated function redisSetBlocking. Just use the new redisSetPipeline.

Details

The rredis client blocks for a response from a connected Redis server after each transaction in non-pipelined mode (the default). When in pipelined mode, transactions are issued without servicing Redis server responses, and server responses must be manually serviced with the redisGetResponse function.

Pipelined mode can improve performance in some circumstances like lots of repeated redisSet operations. When using pipelined mode, don't forget to periodically service responses from the Redis server (results are cached on the server until requested).

Note that use of commands like redisMSet can sometimes obviate the need to use non-blocking mode.

Value

The new pipeline mode (TRUE/FALSE) is invisibly returned.

Note

The function name redisSetBlocking is deprecated and will be replaced in a future version by redisSetPipeline.

Author(s)

B. W. Lewis

See Also

redisGetResponse

Examples

1
2
3
4
5
6
7
8
9

rredis documentation built on May 2, 2019, 2:02 p.m.