Zygo

I run bees on backup servers, mail servers, web hosts, CI build servers, database servers, VM hosts, developer workstations, even on a few IoT devices that boot from SD cards....

Most of the write latency in the `datacow` case comes from processing delayed refs, the rest comes from allocation performance issues. Since kernel 5.0, writers are allowed to queue up...

It can take a while on larger filesystems. Here is a graph of space freed over time on a 148GB test filesystem:  If...

That log snippet shows we're freeing up a few MB/s of references. Try: ``` btrfs ins log $((0x15c58e8f0000)) /run/bees/mnt/c4a6a2c9-5cf0-49b8-812a-0784953f9ba3 btrfs ins log $((0x118f0e51c000)) /run/bees/mnt/c4a6a2c9-5cf0-49b8-812a-0784953f9ba3 ``` This will indicate how many...

Space returns to the filesystem only when the reference count on the dst extent reaches 0. That can take a long time with snapshots. Each snapshot adds more time, so...

810GB * 50 snapshots is 40TB of data to scan in the current implementation, plus the other 7.19 TB of data is almost 50TB. Typical scan speed is 10MB/s, which...

There are rates for how many milliseconds per second are spent hashing. e.g. to see how much time block reads are taking, look for `block_ms` in the `RATES` section of...

Support for xxhash, sha256, and blake2b is easy enough to do standalone, and makes some sense to do separately from the other changes. They are just 1:1 replacements for the...

With crc32c csums on a 16TB filesystem, step 1 always matches every block, so we always get to step 2 where we read the block. If the reads at step...

Oops, wrong math at the end: crc32c really means the practical size cap 32 - 16 = 16 bits, or 65536 * 4096 = 256MB, after that it starts to...