|
This version is still in development and is not considered stable yet. For the latest stable version, please use RIOT-X 2.0! |
Redis URI
RIOT-X follows the Redis URI specification, which supports standalone, sentinel and cluster Redis deployments with plain, SSL, TLS and unix domain socket connections.
You can use the host:port short hand for redis://host:port.
|
- Redis Standalone
-
redis :// [[username :] password@] host [:port][/database] [?[timeout=timeout[d|h|m|s|ms|us|ns]] [&clientName=clientName] [&libraryName=libraryName] [&libraryVersion=libraryVersion] ] - Redis Standalone (SSL)
-
rediss :// [[username :] password@] host [: port][/database] [?[timeout=timeout[d|h|m|s|ms|us|ns]] [&clientName=clientName] [&libraryName=libraryName] [&libraryVersion=libraryVersion] ] - Redis Sentinel
-
redis-sentinel :// [[username :] password@] host1[:port1] [, host2[:port2]] [, hostN[:portN]] [/database] [?[timeout=timeout[d|h|m|s|ms|us|ns]] [&sentinelMasterId=sentinelMasterId] [&clientName=clientName] [&libraryName=libraryName] [&libraryVersion=libraryVersion] ]
You can provide the database, password and timeouts within the Redis URI. For example redis://localhost:6379/1 selects database 1.
|
d
|
Days |
h
|
Hours |
m
|
Minutes |
s
|
Seconds |
ms
|
Milliseconds |
us
|
Microseconds |
ns
|
Nanoseconds |
Client Thread Pools
sync and pubsub in both distributions, and compare in riot, accept
--source-io-threads, --source-threads,
--target-io-threads, and --target-threads.
Single-endpoint commands in riot accept --io-threads and
--threads.
I/O threads run Lettuce’s network event loops. Computation threads handle its
computation and event work. The settings apply independently to each endpoint’s
client resources; they do not control the number of reader/writer connections
or generator worker threads. Each value must be at least 2.
When omitted, the existing Lettuce defaults are preserved. Without a JVM
override, each pool defaults to max(2, available processors).
-Dio.netty.eventLoopThreads changes the defaults for both pools; an explicit
CLI option overrides only its corresponding pool and endpoint.
riotx sync --mode live --in-flight 2048 \
--source-io-threads 4 --source-threads 4 \
--target-io-threads 4 --target-threads 4 \
localhost:6379 localhost:6380
This profile was measured with 100-byte string values on a local host. Choose pool sizes for the workload and available CPU rather than treating it as a universal default.