Configuration Parameters

RedisTimeSeries supports multiple module configuration parameters. All of these parameters can only be set at load-time.

Setting configuration parameters on module load

Setting configuration parameters at load-time is done by appending arguments after the --loadmodule argument when starting a server from the command line or after the loadmodule directive in a Redis config file. For example:

In redis.conf:

loadmodule ./ [OPT VAL]...

From the Redis CLI, using the MODULE LOAD command:> MODULE LOAD [OPT VAL]...

From the command line:

$ redis-server --loadmodule ./ [OPT VAL]...

RedisTimeSeries configuration parameters

The following table summerizes which configuration parameters can be set at module load-time and which can be set on run-time:

Configuration ParameterLoad-timeRun-time


The maximal number of per-shard threads for cross-key queries when using cluster mode (TS.MRANGE, TS.MGET, and TS.QUERYINDEX). The value must be equal to or greater than 1. Note that increasing this value may either increase or decrease the performance!




$ redis-server --loadmodule ./ NUM_THREADS 3


Default compaction rules for newly created key with TS.ADD.

Each rule is separated by a semicolon (;), the rule consists of multiple fields that are separated by a colon (:):

  • Aggregation type: One of the following:

    avgarithmetic mean of all values
    sumsum of all values
    minminimum value
    maxmaximum value
    rangedifference between the highest and the lowest value
    countnumber of values
    firstthe value with the lowest timestamp in the bucket
    lastthe value with the highest timestamp in the bucket
    std.ppopulation standard deviation of the values
    std.ssample standard deviation of the values
    var.ppopulation variance of the values
    var.ssample variance of the values
    twatime-weighted average of all values (since RedisTimeSeries v1.8)
  • Duration of each time bucket - number and the time representation (Example for 1 minute: 1M)

    • m - millisecond
    • M - minute
    • s - seconds
    • d - day
  • Retention time - in milliseconds

  • (since RedisTimeSeries v1.8):

    Optional: Time bucket alignment - number and the time representation (Example for 1 minute: 1M)

    • m - millisecond
    • M - minute
    • s - seconds
    • d - day

    Assure that there is a bucket that starts at exactly alignTimestamp and align all other buckets accordingly. Units: milliseconds. Default value: 0 (aligned with the epoch). Example: if bucketDuration is 24 hours (24 * 3600 * 1000), setting alignTimestamp to 6 hours after the epoch (6 * 3600 * 1000) will ensure that each bucket’s timeframe is [06:00 .. 06:00).

When a compaction policy is defined, compaction rules will be created automatically for newly created time series, and their key would be set to:

  • Before RedisTimeSeries v1.8:

    key_dur_agg where key is the key of the source time series, dur is the bucket duration, and agg is the aggregator.

  • Since RedisTimeSeries v1.8:

    key_dur_agg_aln where key is the key of the source time series, dur is the bucket duration, agg is the aggregator, and aln is the alignment timestamp.


  • max:1M:1h - Aggregate using max over one minute and retain the last hour
  • twa:1d:0:360M - Aggregate daily [06:00 .. 06:00) using time-weighted average; no expiration


No compaction rules.


$ redis-server --loadmodule ./ COMPACTION_POLICY max:1m:1h;min:10s:5d:10d;last:5M:10ms;avg:2h:10d;avg:3d:100d


Maximum age for samples compared to last event time (in milliseconds) per key, this configuration will set the default retention for newly created keys that do not have a an override.




$ redis-server --loadmodule ./ RETENTION_POLICY 20


Policy that will define handling of duplicate samples. The following are the possible policies:

  • BLOCK - an error will occur for any out of order sample
  • FIRST - ignore the new value
  • LAST - override with latest value
  • MIN - only override if the value is lower than the existing value
  • MAX - only override if the value is higher than the existing value
  • SUM - If a previous sample exists, add the new sample to it so that the updated value is equal to (previous + new). If no previous sample exists, set the updated value equal to the new value.

Precedence order

Since the duplication policy can be provided at different levels, the actual precedence of the used policy will be:

  1. TS.ADD input
  2. Key level policy
  3. Module configuration (AKA database-wide)

Default configuration

The default policy for database-wide is BLOCK, new and pre-existing keys will conform to database-wide default policy.


$ redis-server --loadmodule ./ DUPLICATE_POLICY LAST


Default chunk type for automatically created keys when COMPACTION_POLICY is configured. Possible values: COMPRESSED, UNCOMPRESSED.




$ redis-server --loadmodule ./ COMPACTION_POLICY max:1m:1h; CHUNK_TYPE COMPRESSED