---
acl_categories:
- '@bloom'
- '@write'
- '@fast'
arguments:
- name: key
type: key
- name: error_rate
type: double
- name: capacity
type: integer
- name: expansion
optional: true
token: EXPANSION
type: integer
- name: nonscaling
optional: true
token: NONSCALING
type: pure-token
categories:
- docs
- develop
- stack
- oss
- rs
- rc
- oss
- kubernetes
- clients
complexity: O(1)
description: Creates a new Bloom Filter
group: bf
hidden: false
linkTitle: BF.RESERVE
module: Bloom
railroad_diagram: /images/railroad/bf.reserve.svg
since: 1.0.0
stack_path: docs/data-types/probabilistic
summary: Creates a new Bloom Filter
syntax_fmt: "BF.RESERVE key error_rate capacity [EXPANSION\_expansion]\n [NONSCALING]"
title: BF.RESERVE
---
Creates an empty Bloom filter with a single sub-filter for the initial specified capacity and with an upper bound `error_rate`.
By default, the filter auto-scales by creating additional sub-filters when `capacity` is reached.
The new sub-filter is created with size of the previous sub-filter multiplied by `expansion`.
Though the filter can scale up by creating sub-filters, it is recommended to reserve the estimated required `capacity` since maintaining and querying
sub-filters requires additional memory (each sub-filter uses an extra bits and hash function) and consume further CPU time than an equivalent filter that had
the right capacity at creation time.
The optimal number of hash functions is `ceil(-ln(error_rate) / ln(2))`.
The required number of bits per item, given the desired `error_rate` and the optimal number of hash functions, is `-ln(error_rate) / ln(2)^2`. Hence, the required number of bits in the filter is `capacity * -ln(error_rate) / ln(2)^2`.
* **1%** error rate requires 7 hash functions and 9.585 bits per item.
* **0.1%** error rate requires 10 hash functions and 14.378 bits per item.
* **0.01%** error rate requires 14 hash functions and 19.170 bits per item.
## Required arguments
key
is key name for the the Bloom filter to be created.
error_rate
The desired probability for false positives. The rate is a decimal value between 0 and 1.
For example, for a desired false positive rate of 0.1% (1 in 1000), error_rate should be set to 0.001.
capacity
The number of entries intended to be added to the filter.
If your filter allows scaling, performance will begin to degrade after adding more items than this number.
The actual degradation depends on how far the limit has been exceeded. Performance degrades linearly with the number of `sub-filters`.
## Optional arguments
NONSCALING
Prevents the filter from creating additional sub-filters if initial capacity is reached.
Non-scaling filters requires slightly less memory than their scaling counterparts. The filter returns an error when `capacity` is reached.
EXPANSION expansion
When `capacity` is reached, an additional sub-filter is created.
The size of the new sub-filter is the size of the last sub-filter multiplied by `expansion`, specified as a positive integer.
If the number of items to be stored in the filter is unknown, you use an `expansion` of `2` or more to reduce the number of sub-filters.
Otherwise, you use an `expansion` of `1` to reduce memory consumption. The default value is `2`.
## Examples
{{< highlight bash >}}
redis> BF.RESERVE bf 0.01 1000
OK
{{< / highlight >}}
{{< highlight bash >}}
redis> BF.RESERVE bf 0.01 1000
(error) ERR item exists
{{< / highlight >}}
{{< highlight bash >}}
redis> BF.RESERVE bf_exp 0.01 1000 EXPANSION 2
OK
{{< / highlight >}}
{{< highlight bash >}}
redis> BF.RESERVE bf_non 0.01 1000 NONSCALING
OK
{{< / highlight >}}
## Redis Software and Redis Cloud compatibility
| Redis
Software | Redis
Cloud | Notes |
|:----------------------|:-----------------|:------|
| ✅ Supported
| ✅ Flexible & Annual
✅ Free & Fixed | |
## Return information
{{< multitabs id="bf-reserve-return-info"
tab1="RESP2"
tab2="RESP3" >}}
One of the following:
* [Simple string reply]({{< relref "/develop/reference/protocol-spec#simple-strings" >}}): `OK` if the filter was created successfully.
* [Simple error reply]({{< relref "/develop/reference/protocol-spec#simple-errors" >}}) in these cases: invalid arguments or the key already exists.
-tab-sep-
One of the following:
* [Simple string reply]({{< relref "/develop/reference/protocol-spec#simple-strings" >}}): `OK` if the filter was created successfully.
* [Simple error reply]({{< relref "/develop/reference/protocol-spec#simple-errors" >}}) in these cases: invalid arguments or the key already exists.
{{< /multitabs >}}