########
# bees configuration file
#
# Bees documentation for configuration
# and command line options is available at:
# https://zygo.github.io/bees/options.html
# https://zygo.github.io/bees/config.html
########

# Bees works on a filesystem as a whole. We use
# the filesystems unique UUID to identify which
# filesystem we want.
# Use `btrfs filesyatem show` to see currently
# known btrfs fikesystems' UUID's.
#fsuuid="df68a30d-d26e-4b9c-9606-a130e66ce63d"

# The size of bees hash table in bytes.
# Must be a multiple of 128KiB. See the chart
# below for recommended sizes.
#hashsize="$((512*1024*1024))" # 512MiB

# Set bees loglevel.
# 1 is lowest, 8 is most verbose.
# WARNING: a high loglevel increases logfile size greatly.
#loglevel="8"

# Extra bees command line arguments
#bees_args="-m 3"

# Location of the bees status file
#statusfile="/run/bees/${fsuuid}.status"

# Custom logfile location
#logfile="/var/log/bees/${RC_SVCNAME}.log"

## OpenRC resource control
# Do not set memory.x too low as bees needs to fit
# the entire hash database in memory.

# This example requires that
# rc_cgroup_mode="unified" is set
# in rc.conf
#rc_cgroup_settings="
#cpu.idle 1
#io.weight 1
#io.bfq.weight 1
#œmemory.high 1G
#memory.max 2G
#"

## Hash table sizing
# The relative size of the hash table
# comared to the data set determines
# the achievable dedup block size. 
# A good starting point is 128K

# A = unique data size
# B = hash table size
# C = average dedupe extent size
#   A  |   B   |   C
# --------------------
#  1TB |   4GB |    4K
#  1TB |   1GB |   16K
#  1TB | 256MB |   64K
#  1TB | 128MB |  128K <- recommended
#  1TB |  16MB | 1024K
# 64TB |   1GB | 1024K