2020-10-26 04:43:04 +01:00
|
|
|
// Copyright (c) Facebook, Inc. and its affiliates. All Rights Reserved.
|
|
|
|
// This source code is licensed under both the GPLv2 (found in the
|
|
|
|
// COPYING file in the root directory) and Apache 2.0 License
|
|
|
|
// (found in the LICENSE.Apache file in the root directory).
|
|
|
|
|
|
|
|
#pragma once
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
#include <cmath>
|
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
#include "port/port.h" // for PREFETCH
|
|
|
|
#include "util/ribbon_alg.h"
|
|
|
|
|
|
|
|
namespace ROCKSDB_NAMESPACE {
|
|
|
|
|
|
|
|
namespace ribbon {
|
|
|
|
|
|
|
|
// RIBBON PHSF & RIBBON Filter (Rapid Incremental Boolean Banding ON-the-fly)
|
|
|
|
//
|
|
|
|
// ribbon_impl.h: templated (parameterized) standard implementations
|
|
|
|
//
|
|
|
|
// Ribbon is a Perfect Hash Static Function construction useful as a compact
|
|
|
|
// static Bloom filter alternative. See ribbon_alg.h for core algorithms
|
|
|
|
// and core design details.
|
|
|
|
//
|
|
|
|
// TODO: more details on trade-offs and practical issues.
|
|
|
|
|
|
|
|
// Ribbon implementations in this file take these parameters, which must be
|
|
|
|
// provided in a class/struct type with members expressed in this concept:
|
|
|
|
|
|
|
|
// concept TypesAndSettings {
|
|
|
|
// // See RibbonTypes and *Hasher in ribbon_alg.h, except here we have
|
|
|
|
// // the added constraint that Hash be equivalent to either uint32_t or
|
|
|
|
// // uint64_t.
|
|
|
|
// typename Hash;
|
|
|
|
// typename CoeffRow;
|
|
|
|
// typename ResultRow;
|
|
|
|
// typename Index;
|
|
|
|
// typename Key;
|
|
|
|
// static constexpr bool kFirstCoeffAlwaysOne;
|
|
|
|
//
|
|
|
|
// // An unsigned integer type for identifying a hash seed, typically
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// // uint32_t or uint64_t. Importantly, this is the amount of data
|
|
|
|
// // stored in memory for identifying a raw seed. See StandardHasher.
|
2020-10-26 04:43:04 +01:00
|
|
|
// typename Seed;
|
|
|
|
//
|
|
|
|
// // When true, the PHSF implements a static filter, expecting just
|
|
|
|
// // keys as inputs for construction. When false, implements a general
|
|
|
|
// // PHSF and expects std::pair<Key, ResultRow> as inputs for
|
|
|
|
// // construction.
|
|
|
|
// static constexpr bool kIsFilter;
|
|
|
|
//
|
|
|
|
// // When true, adds a tiny bit more hashing logic on queries and
|
|
|
|
// // construction to improve utilization at the beginning and end of
|
|
|
|
// // the structure. Recommended when CoeffRow is only 64 bits (or
|
|
|
|
// // less), so typical num_starts < 10k.
|
|
|
|
// static constexpr bool kUseSmash;
|
|
|
|
//
|
2020-11-03 21:45:18 +01:00
|
|
|
// // When true, allows number of "starts" to be zero, for best support
|
|
|
|
// // of the "no keys to add" case by always returning false for filter
|
|
|
|
// // queries. (This is distinct from the "keys added but no space for
|
|
|
|
// // any data" case, in which a filter always returns true.) The cost
|
|
|
|
// // supporting this is a conditional branch (probably predictable) in
|
|
|
|
// // queries.
|
|
|
|
// static constexpr bool kAllowZeroStarts;
|
|
|
|
//
|
2020-10-26 04:43:04 +01:00
|
|
|
// // A seedable stock hash function on Keys. All bits of Hash must
|
|
|
|
// // be reasonably high quality. XXH functions recommended, but
|
|
|
|
// // Murmur, City, Farm, etc. also work.
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// static Hash HashFn(const Key &, Seed raw_seed);
|
2020-10-26 04:43:04 +01:00
|
|
|
// };
|
|
|
|
|
|
|
|
// A bit of a hack to automatically construct the type for
|
|
|
|
// AddInput based on a constexpr bool.
|
|
|
|
template <typename Key, typename ResultRow, bool IsFilter>
|
|
|
|
struct AddInputSelector {
|
|
|
|
// For general PHSF, not filter
|
|
|
|
using T = std::pair<Key, ResultRow>;
|
|
|
|
};
|
|
|
|
|
|
|
|
template <typename Key, typename ResultRow>
|
|
|
|
struct AddInputSelector<Key, ResultRow, true /*IsFilter*/> {
|
|
|
|
// For Filter
|
|
|
|
using T = Key;
|
|
|
|
};
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
// To avoid writing 'typename' everywhere that we use types like 'Index'
|
2020-10-26 04:43:04 +01:00
|
|
|
#define IMPORT_RIBBON_TYPES_AND_SETTINGS(TypesAndSettings) \
|
|
|
|
using CoeffRow = typename TypesAndSettings::CoeffRow; \
|
|
|
|
using ResultRow = typename TypesAndSettings::ResultRow; \
|
|
|
|
using Index = typename TypesAndSettings::Index; \
|
|
|
|
using Hash = typename TypesAndSettings::Hash; \
|
|
|
|
using Key = typename TypesAndSettings::Key; \
|
|
|
|
using Seed = typename TypesAndSettings::Seed; \
|
|
|
|
\
|
|
|
|
/* Some more additions */ \
|
|
|
|
using QueryInput = Key; \
|
|
|
|
using AddInput = typename ROCKSDB_NAMESPACE::ribbon::AddInputSelector< \
|
|
|
|
Key, ResultRow, TypesAndSettings::kIsFilter>::T; \
|
|
|
|
static constexpr auto kCoeffBits = \
|
|
|
|
static_cast<Index>(sizeof(CoeffRow) * 8U); \
|
|
|
|
\
|
|
|
|
/* Export to algorithm */ \
|
|
|
|
static constexpr bool kFirstCoeffAlwaysOne = \
|
|
|
|
TypesAndSettings::kFirstCoeffAlwaysOne; \
|
|
|
|
\
|
|
|
|
static_assert(sizeof(CoeffRow) + sizeof(ResultRow) + sizeof(Index) + \
|
|
|
|
sizeof(Hash) + sizeof(Key) + sizeof(Seed) + \
|
|
|
|
sizeof(QueryInput) + sizeof(AddInput) + kCoeffBits + \
|
|
|
|
kFirstCoeffAlwaysOne > \
|
|
|
|
0, \
|
|
|
|
"avoid unused warnings, semicolon expected after macro call")
|
|
|
|
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
#ifdef _MSC_VER
|
|
|
|
#pragma warning(push)
|
|
|
|
#pragma warning(disable : 4309) // cast truncating constant
|
|
|
|
#pragma warning(disable : 4307) // arithmetic constant overflow
|
|
|
|
#endif
|
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
// StandardHasher: A standard implementation of concepts RibbonTypes,
|
|
|
|
// PhsfQueryHasher, FilterQueryHasher, and BandingHasher from ribbon_alg.h.
|
|
|
|
//
|
|
|
|
// This implementation should be suitable for most all practical purposes
|
|
|
|
// as it "behaves" across a wide range of settings, with little room left
|
|
|
|
// for improvement. The key functionality in this hasher is generating
|
|
|
|
// CoeffRows, starts, and (for filters) ResultRows, which could be ~150
|
|
|
|
// bits of data or more, from a modest hash of 64 or even just 32 bits, with
|
|
|
|
// enough uniformity and bitwise independence to be close to "the best you
|
|
|
|
// can do" with available hash information in terms of FP rate and
|
|
|
|
// compactness. (64 bits recommended and sufficient for PHSF practical
|
|
|
|
// purposes.)
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
//
|
|
|
|
// Another feature of this hasher is a minimal "premixing" of seeds before
|
|
|
|
// they are provided to TypesAndSettings::HashFn in case that function does
|
|
|
|
// not provide sufficiently independent hashes when iterating merely
|
|
|
|
// sequentially on seeds. (This for example works around a problem with the
|
|
|
|
// preview version 0.7.2 of XXH3 used in RocksDB, a.k.a. XXH3p or Hash64, and
|
|
|
|
// MurmurHash1 used in RocksDB, a.k.a. Hash.) We say this pre-mixing step
|
|
|
|
// translates "ordinal seeds," which we iterate sequentially to find a
|
|
|
|
// solution, into "raw seeds," with many more bits changing for each
|
|
|
|
// iteration. The translation is an easily reversible lightweight mixing,
|
|
|
|
// not suitable for hashing on its own. An advantage of this approach is that
|
|
|
|
// StandardHasher can store just the raw seed (e.g. 64 bits) for fast query
|
|
|
|
// times, while from the application perspective, we can limit to a small
|
|
|
|
// number of ordinal keys (e.g. 64 in 6 bits) for saving in metadata.
|
|
|
|
//
|
|
|
|
// The default constructor initializes the seed to ordinal seed zero, which
|
|
|
|
// is equal to raw seed zero.
|
|
|
|
//
|
2020-10-26 04:43:04 +01:00
|
|
|
template <class TypesAndSettings>
|
|
|
|
class StandardHasher {
|
|
|
|
public:
|
|
|
|
IMPORT_RIBBON_TYPES_AND_SETTINGS(TypesAndSettings);
|
|
|
|
|
|
|
|
inline Hash GetHash(const Key& key) const {
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
return TypesAndSettings::HashFn(key, raw_seed_);
|
2020-10-26 04:43:04 +01:00
|
|
|
};
|
|
|
|
// For when AddInput == pair<Key, ResultRow> (kIsFilter == false)
|
|
|
|
inline Hash GetHash(const std::pair<Key, ResultRow>& bi) const {
|
|
|
|
return GetHash(bi.first);
|
|
|
|
};
|
|
|
|
inline Index GetStart(Hash h, Index num_starts) const {
|
|
|
|
// This is "critical path" code because it's required before memory
|
|
|
|
// lookup.
|
|
|
|
//
|
|
|
|
// FastRange gives us a fast and effective mapping from h to the
|
2020-11-03 21:45:18 +01:00
|
|
|
// appropriate range. This depends most, sometimes exclusively, on
|
2020-10-26 04:43:04 +01:00
|
|
|
// upper bits of h.
|
|
|
|
//
|
|
|
|
if (TypesAndSettings::kUseSmash) {
|
|
|
|
// Extra logic to "smash" entries at beginning and end, for
|
|
|
|
// better utilization. For example, without smash and with
|
|
|
|
// kFirstCoeffAlwaysOne, there's about a 30% chance that the
|
|
|
|
// first slot in the banding will be unused, and worse without
|
|
|
|
// kFirstCoeffAlwaysOne. The ending slots are even less utilized
|
|
|
|
// without smash.
|
|
|
|
//
|
|
|
|
// But since this only affects roughly kCoeffBits of the slots,
|
|
|
|
// it's usually small enough to be ignorable (less computation in
|
|
|
|
// this function) when number of slots is roughly 10k or larger.
|
|
|
|
//
|
2020-11-03 21:45:18 +01:00
|
|
|
// The best values for these smash weights might depend on how
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
// densely you're packing entries, and also kCoeffBits, but this
|
|
|
|
// seems to work well for roughly 95% success probability.
|
2020-10-26 04:43:04 +01:00
|
|
|
//
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
constexpr Index kFrontSmash = kCoeffBits / 4;
|
|
|
|
constexpr Index kBackSmash = kCoeffBits / 4;
|
2020-10-26 04:43:04 +01:00
|
|
|
Index start = FastRangeGeneric(h, num_starts + kFrontSmash + kBackSmash);
|
|
|
|
start = std::max(start, kFrontSmash);
|
|
|
|
start -= kFrontSmash;
|
|
|
|
start = std::min(start, num_starts - 1);
|
|
|
|
return start;
|
|
|
|
} else {
|
|
|
|
// For query speed, we allow small number of initial and final
|
|
|
|
// entries to be under-utilized.
|
|
|
|
// NOTE: This call statically enforces that Hash is equivalent to
|
|
|
|
// either uint32_t or uint64_t.
|
|
|
|
return FastRangeGeneric(h, num_starts);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
inline CoeffRow GetCoeffRow(Hash h) const {
|
|
|
|
// This is not so much "critical path" code because it can be done in
|
|
|
|
// parallel (instruction level) with memory lookup.
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
//
|
|
|
|
// We do not need exhaustive remixing for CoeffRow, but just enough that
|
|
|
|
// (a) every bit is reasonably independent from Start.
|
|
|
|
// (b) every Hash-length bit subsequence of the CoeffRow has full or
|
|
|
|
// nearly full entropy from h.
|
|
|
|
// (c) if nontrivial bit subsequences within are correlated, it needs to
|
|
|
|
// be more complicated than exact copy or bitwise not (at least without
|
|
|
|
// kFirstCoeffAlwaysOne), or else there seems to be a kind of
|
|
|
|
// correlated clustering effect.
|
|
|
|
// (d) the CoeffRow is not zero, so that no one input on its own can
|
|
|
|
// doom construction success. (Preferably a mix of 1's and 0's if
|
|
|
|
// satisfying above.)
|
|
|
|
|
|
|
|
// First, establish sufficient bitwise independence from Start, with
|
|
|
|
// multiplication by a large random prime.
|
|
|
|
// Note that we cast to Hash because if we use product bits beyond
|
|
|
|
// original input size, that's going to correlate with Start (FastRange)
|
|
|
|
// even with a (likely) different multiplier here.
|
|
|
|
Hash a = h * kCoeffAndResultFactor;
|
|
|
|
|
|
|
|
// If that's big enough, we're done. If not, we have to expand it,
|
|
|
|
// maybe up to 4x size.
|
|
|
|
uint64_t b = a;
|
|
|
|
static_assert(
|
|
|
|
sizeof(Hash) == sizeof(uint64_t) || sizeof(Hash) == sizeof(uint32_t),
|
|
|
|
"Supported sizes");
|
|
|
|
if (sizeof(Hash) < sizeof(uint64_t)) {
|
|
|
|
// Almost-trivial hash expansion (OK - see above), favoring roughly
|
|
|
|
// equal number of 1's and 0's in result
|
|
|
|
b = (b << 32) ^ b ^ kCoeffXor32;
|
|
|
|
}
|
|
|
|
Unsigned128 c = b;
|
|
|
|
static_assert(sizeof(CoeffRow) == sizeof(uint64_t) ||
|
|
|
|
sizeof(CoeffRow) == sizeof(Unsigned128),
|
|
|
|
"Supported sizes");
|
|
|
|
if (sizeof(uint64_t) < sizeof(CoeffRow)) {
|
|
|
|
// Almost-trivial hash expansion (OK - see above), favoring roughly
|
|
|
|
// equal number of 1's and 0's in result
|
|
|
|
c = (c << 64) ^ c ^ kCoeffXor64;
|
|
|
|
}
|
|
|
|
auto cr = static_cast<CoeffRow>(c);
|
|
|
|
|
|
|
|
// Now ensure the value is non-zero
|
2020-10-26 04:43:04 +01:00
|
|
|
if (kFirstCoeffAlwaysOne) {
|
|
|
|
cr |= 1;
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
} else if (sizeof(CoeffRow) == sizeof(Hash)) {
|
|
|
|
// Still have to ensure some bit is non-zero
|
|
|
|
cr |= (cr == 0) ? 1 : 0;
|
2020-10-26 04:43:04 +01:00
|
|
|
} else {
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// (We did trivial expansion with constant xor, which ensures some
|
|
|
|
// bits are non-zero.)
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
return cr;
|
|
|
|
}
|
|
|
|
inline ResultRow GetResultRowMask() const {
|
2020-11-03 21:45:18 +01:00
|
|
|
// TODO: will be used with InterleavedSolutionStorage?
|
2020-10-26 04:43:04 +01:00
|
|
|
// For now, all bits set (note: might be a small type so might need to
|
|
|
|
// narrow after promotion)
|
|
|
|
return static_cast<ResultRow>(~ResultRow{0});
|
|
|
|
}
|
|
|
|
inline ResultRow GetResultRowFromHash(Hash h) const {
|
|
|
|
if (TypesAndSettings::kIsFilter) {
|
|
|
|
// This is not so much "critical path" code because it can be done in
|
|
|
|
// parallel (instruction level) with memory lookup.
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
//
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
// ResultRow bits only needs to be independent from CoeffRow bits if
|
|
|
|
// many entries might have the same start location, where "many" is
|
|
|
|
// comparable to number of hash bits or kCoeffBits. If !kUseSmash
|
|
|
|
// and num_starts > kCoeffBits, it is safe and efficient to draw from
|
|
|
|
// the same bits computed for CoeffRow, which are reasonably
|
|
|
|
// independent from Start. (Inlining and common subexpression
|
|
|
|
// elimination with GetCoeffRow should make this
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// a single shared multiplication in generated code.)
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
//
|
|
|
|
// TODO: fix & test the kUseSmash case with very small num_starts
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
Hash a = h * kCoeffAndResultFactor;
|
|
|
|
// The bits here that are *most* independent of Start are the highest
|
|
|
|
// order bits (as in Knuth multiplicative hash). To make those the
|
|
|
|
// most preferred for use in the result row, we do a bswap here.
|
|
|
|
auto rr = static_cast<ResultRow>(EndianSwapValue(a));
|
2020-10-26 04:43:04 +01:00
|
|
|
return rr & GetResultRowMask();
|
|
|
|
} else {
|
|
|
|
// Must be zero
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// For when AddInput == Key (kIsFilter == true)
|
|
|
|
inline ResultRow GetResultRowFromInput(const Key&) const {
|
|
|
|
// Must be zero
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
// For when AddInput == pair<Key, ResultRow> (kIsFilter == false)
|
|
|
|
inline ResultRow GetResultRowFromInput(
|
|
|
|
const std::pair<Key, ResultRow>& bi) const {
|
|
|
|
// Simple extraction
|
|
|
|
return bi.second;
|
|
|
|
}
|
|
|
|
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// Seed tracking APIs - see class comment
|
|
|
|
void SetRawSeed(Seed seed) { raw_seed_ = seed; }
|
|
|
|
Seed GetRawSeed() { return raw_seed_; }
|
|
|
|
void SetOrdinalSeed(Seed count) {
|
|
|
|
// A simple, reversible mixing of any size (whole bytes) up to 64 bits.
|
|
|
|
// This allows casting the raw seed to any smaller size we use for
|
|
|
|
// ordinal seeds without risk of duplicate raw seeds for unique ordinal
|
|
|
|
// seeds.
|
|
|
|
|
|
|
|
// Seed type might be smaller than numerical promotion size, but Hash
|
|
|
|
// should be at least that size, so we use Hash as intermediate type.
|
|
|
|
static_assert(sizeof(Seed) <= sizeof(Hash),
|
|
|
|
"Hash must be at least size of Seed");
|
|
|
|
|
|
|
|
// Multiply by a large random prime (one-to-one for any prefix of bits)
|
|
|
|
Hash tmp = count * kToRawSeedFactor;
|
|
|
|
// Within-byte one-to-one mixing
|
|
|
|
static_assert((kSeedMixMask & (kSeedMixMask >> kSeedMixShift)) == 0,
|
|
|
|
"Illegal mask+shift");
|
|
|
|
tmp ^= (tmp & kSeedMixMask) >> kSeedMixShift;
|
|
|
|
raw_seed_ = static_cast<Seed>(tmp);
|
|
|
|
// dynamic verification
|
|
|
|
assert(GetOrdinalSeed() == count);
|
|
|
|
}
|
|
|
|
Seed GetOrdinalSeed() {
|
|
|
|
Hash tmp = raw_seed_;
|
|
|
|
// Within-byte one-to-one mixing (its own inverse)
|
|
|
|
tmp ^= (tmp & kSeedMixMask) >> kSeedMixShift;
|
|
|
|
// Multiply by 64-bit multiplicative inverse
|
|
|
|
static_assert(kToRawSeedFactor * kFromRawSeedFactor == Hash{1},
|
|
|
|
"Must be inverses");
|
|
|
|
return static_cast<Seed>(tmp * kFromRawSeedFactor);
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
protected:
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// For expanding hash:
|
|
|
|
// large random prime
|
|
|
|
static constexpr Hash kCoeffAndResultFactor =
|
|
|
|
static_cast<Hash>(0xc28f82822b650bedULL);
|
|
|
|
// random-ish data
|
|
|
|
static constexpr uint32_t kCoeffXor32 = 0xa6293635U;
|
|
|
|
static constexpr uint64_t kCoeffXor64 = 0xc367844a6e52731dU;
|
|
|
|
|
|
|
|
// For pre-mixing seeds
|
|
|
|
static constexpr Hash kSeedMixMask = static_cast<Hash>(0xf0f0f0f0f0f0f0f0ULL);
|
|
|
|
static constexpr unsigned kSeedMixShift = 4U;
|
|
|
|
static constexpr Hash kToRawSeedFactor =
|
|
|
|
static_cast<Hash>(0xc78219a23eeadd03ULL);
|
|
|
|
static constexpr Hash kFromRawSeedFactor =
|
|
|
|
static_cast<Hash>(0xfe1a137d14b475abULL);
|
|
|
|
|
|
|
|
// See class description
|
|
|
|
Seed raw_seed_ = 0;
|
2020-10-26 04:43:04 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
// StandardRehasher (and StandardRehasherAdapter): A variant of
|
|
|
|
// StandardHasher that uses the same type for keys as for hashes.
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// This is primarily intended for building a Ribbon filter
|
|
|
|
// from existing hashes without going back to original inputs in
|
|
|
|
// order to apply a different seed. This hasher seeds a 1-to-1 mixing
|
|
|
|
// transformation to apply a seed to an existing hash. (Untested for
|
|
|
|
// hash-sized keys that are not already uniformly distributed.) This
|
|
|
|
// transformation builds on the seed pre-mixing done in StandardHasher.
|
2020-10-26 04:43:04 +01:00
|
|
|
//
|
2020-11-03 21:45:18 +01:00
|
|
|
// Testing suggests essentially no degradation of solution success rate
|
2020-10-26 04:43:04 +01:00
|
|
|
// vs. going back to original inputs when changing hash seeds. For example:
|
|
|
|
// Average re-seeds for solution with r=128, 1.02x overhead, and ~100k keys
|
|
|
|
// is about 1.10 for both StandardHasher and StandardRehasher.
|
|
|
|
//
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// StandardRehasher is not really recommended for general PHSFs (not
|
|
|
|
// filters) because a collision in the original hash could prevent
|
|
|
|
// construction despite re-seeding the Rehasher. (Such collisions
|
|
|
|
// do not interfere with filter construction.)
|
|
|
|
//
|
2020-10-26 04:43:04 +01:00
|
|
|
// concept RehasherTypesAndSettings: like TypesAndSettings but
|
|
|
|
// does not require Key or HashFn.
|
|
|
|
template <class RehasherTypesAndSettings>
|
|
|
|
class StandardRehasherAdapter : public RehasherTypesAndSettings {
|
|
|
|
public:
|
|
|
|
using Hash = typename RehasherTypesAndSettings::Hash;
|
|
|
|
using Key = Hash;
|
|
|
|
using Seed = typename RehasherTypesAndSettings::Seed;
|
|
|
|
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
static Hash HashFn(const Hash& input, Seed raw_seed) {
|
|
|
|
// Note: raw_seed is already lightly pre-mixed, and this multiplication
|
|
|
|
// by a large prime is sufficient mixing (low-to-high bits) on top of
|
|
|
|
// that for good FastRange results, which depends primarily on highest
|
|
|
|
// bits. (The hashed CoeffRow and ResultRow are less sensitive to
|
|
|
|
// mixing than Start.)
|
|
|
|
// Also note: did consider adding ^ (input >> some) before the
|
|
|
|
// multiplication, but doesn't appear to be necessary.
|
|
|
|
return (input ^ raw_seed) * kRehashFactor;
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
|
|
|
|
private:
|
|
|
|
static constexpr Hash kRehashFactor =
|
|
|
|
static_cast<Hash>(0x6193d459236a3a0dULL);
|
2020-10-26 04:43:04 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
// See comment on StandardRehasherAdapter
|
|
|
|
template <class RehasherTypesAndSettings>
|
|
|
|
using StandardRehasher =
|
|
|
|
StandardHasher<StandardRehasherAdapter<RehasherTypesAndSettings>>;
|
|
|
|
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
#ifdef _MSC_VER
|
|
|
|
#pragma warning(pop)
|
|
|
|
#endif
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
// Especially with smaller hashes (e.g. 32 bit), there can be noticeable
|
|
|
|
// false positives due to collisions in the Hash returned by GetHash.
|
|
|
|
// This function returns the expected FP rate due to those collisions,
|
|
|
|
// which can be added to the expected FP rate from the underlying data
|
|
|
|
// structure. (Note: technically, a + b is only a good approximation of
|
|
|
|
// 1-(1-a)(1-b) == a + b - a*b, if a and b are much closer to 0 than to 1.)
|
|
|
|
// The number of entries added can be a double here in case it's an
|
|
|
|
// average.
|
|
|
|
template <class Hasher, typename Numerical>
|
|
|
|
double ExpectedCollisionFpRate(const Hasher& hasher, Numerical added) {
|
|
|
|
// Standardize on the 'double' specialization
|
|
|
|
return ExpectedCollisionFpRate(hasher, 1.0 * added);
|
|
|
|
}
|
|
|
|
template <class Hasher>
|
|
|
|
double ExpectedCollisionFpRate(const Hasher& /*hasher*/, double added) {
|
|
|
|
// Technically, there could be overlap among the added, but ignoring that
|
|
|
|
// is typically close enough.
|
|
|
|
return added / std::pow(256.0, sizeof(typename Hasher::Hash));
|
|
|
|
}
|
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
// StandardBanding: a canonical implementation of BandingStorage and
|
|
|
|
// BacktrackStorage, with convenience API for banding (solving with on-the-fly
|
|
|
|
// Gaussian elimination) with and without backtracking.
|
|
|
|
template <class TypesAndSettings>
|
|
|
|
class StandardBanding : public StandardHasher<TypesAndSettings> {
|
|
|
|
public:
|
|
|
|
IMPORT_RIBBON_TYPES_AND_SETTINGS(TypesAndSettings);
|
|
|
|
|
|
|
|
StandardBanding(Index num_slots = 0, Index backtrack_size = 0) {
|
2020-11-03 21:45:18 +01:00
|
|
|
Reset(num_slots, backtrack_size);
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
void Reset(Index num_slots, Index backtrack_size = 0) {
|
2020-11-03 21:45:18 +01:00
|
|
|
if (num_slots == 0) {
|
|
|
|
// Unusual (TypesAndSettings::kAllowZeroStarts) or "uninitialized"
|
|
|
|
num_starts_ = 0;
|
2020-10-26 04:43:04 +01:00
|
|
|
} else {
|
2020-11-03 21:45:18 +01:00
|
|
|
// Normal
|
|
|
|
assert(num_slots >= kCoeffBits);
|
|
|
|
if (num_slots > num_slots_allocated_) {
|
|
|
|
coeff_rows_.reset(new CoeffRow[num_slots]());
|
|
|
|
// Note: don't strictly have to zero-init result_rows,
|
|
|
|
// except possible information leakage ;)
|
|
|
|
result_rows_.reset(new ResultRow[num_slots]());
|
|
|
|
num_slots_allocated_ = num_slots;
|
|
|
|
} else {
|
|
|
|
for (Index i = 0; i < num_slots; ++i) {
|
|
|
|
coeff_rows_[i] = 0;
|
|
|
|
// Note: don't strictly have to zero-init result_rows
|
|
|
|
result_rows_[i] = 0;
|
|
|
|
}
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
2020-11-03 21:45:18 +01:00
|
|
|
num_starts_ = num_slots - kCoeffBits + 1;
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
EnsureBacktrackSize(backtrack_size);
|
|
|
|
}
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
void EnsureBacktrackSize(Index backtrack_size) {
|
|
|
|
if (backtrack_size > backtrack_size_) {
|
|
|
|
backtrack_.reset(new Index[backtrack_size]);
|
|
|
|
backtrack_size_ = backtrack_size;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// ********************************************************************
|
|
|
|
// From concept BandingStorage
|
|
|
|
|
|
|
|
inline bool UsePrefetch() const {
|
2020-11-03 21:45:18 +01:00
|
|
|
// A rough guesstimate of when prefetching during construction pays off.
|
2020-10-26 04:43:04 +01:00
|
|
|
// TODO: verify/validate
|
|
|
|
return num_starts_ > 1500;
|
|
|
|
}
|
|
|
|
inline void Prefetch(Index i) const {
|
|
|
|
PREFETCH(&coeff_rows_[i], 1 /* rw */, 1 /* locality */);
|
|
|
|
PREFETCH(&result_rows_[i], 1 /* rw */, 1 /* locality */);
|
|
|
|
}
|
|
|
|
inline CoeffRow* CoeffRowPtr(Index i) { return &coeff_rows_[i]; }
|
|
|
|
inline ResultRow* ResultRowPtr(Index i) { return &result_rows_[i]; }
|
|
|
|
inline Index GetNumStarts() const { return num_starts_; }
|
|
|
|
|
|
|
|
// from concept BacktrackStorage, for when backtracking is used
|
|
|
|
inline bool UseBacktrack() const { return true; }
|
|
|
|
inline void BacktrackPut(Index i, Index to_save) { backtrack_[i] = to_save; }
|
|
|
|
inline Index BacktrackGet(Index i) const { return backtrack_[i]; }
|
|
|
|
|
|
|
|
// ********************************************************************
|
|
|
|
// Some useful API, still somewhat low level. Here an input is
|
|
|
|
// a Key for filters, or std::pair<Key, ResultRow> for general PHSF.
|
|
|
|
|
|
|
|
// Adds a range of inputs to the banding, returning true if successful.
|
|
|
|
// False means none or some may have been successfully added, so it's
|
|
|
|
// best to Reset this banding before any further use.
|
|
|
|
//
|
|
|
|
// Adding can fail even before all the "slots" are completely "full".
|
|
|
|
//
|
|
|
|
template <typename InputIterator>
|
|
|
|
bool AddRange(InputIterator begin, InputIterator end) {
|
2020-11-03 21:45:18 +01:00
|
|
|
assert(num_starts_ > 0 || TypesAndSettings::kAllowZeroStarts);
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual. Can't add any in this case.
|
|
|
|
return begin == end;
|
|
|
|
}
|
|
|
|
// Normal
|
2020-10-26 04:43:04 +01:00
|
|
|
return BandingAddRange(this, *this, begin, end);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Adds a range of inputs to the banding, returning true if successful,
|
|
|
|
// or if unsuccessful, rolls back to state before this call and returns
|
|
|
|
// false. Caller guarantees that the number of inputs in this batch
|
|
|
|
// does not exceed `backtrack_size` provided to Reset.
|
|
|
|
//
|
|
|
|
// Adding can fail even before all the "slots" are completely "full".
|
|
|
|
//
|
|
|
|
template <typename InputIterator>
|
|
|
|
bool AddRangeOrRollBack(InputIterator begin, InputIterator end) {
|
2020-11-03 21:45:18 +01:00
|
|
|
assert(num_starts_ > 0 || TypesAndSettings::kAllowZeroStarts);
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual. Can't add any in this case.
|
|
|
|
return begin == end;
|
|
|
|
}
|
|
|
|
// else Normal
|
2020-10-26 04:43:04 +01:00
|
|
|
return BandingAddRange(this, this, *this, begin, end);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Adds a single input to the banding, returning true if successful.
|
|
|
|
// If unsuccessful, returns false and banding state is unchanged.
|
|
|
|
//
|
|
|
|
// Adding can fail even before all the "slots" are completely "full".
|
|
|
|
//
|
2020-11-03 21:45:18 +01:00
|
|
|
bool Add(const AddInput& input) {
|
|
|
|
// Pointer can act as iterator
|
|
|
|
return AddRange(&input, &input + 1);
|
|
|
|
}
|
2020-10-26 04:43:04 +01:00
|
|
|
|
|
|
|
// Return the number of "occupied" rows (with non-zero coefficients stored).
|
|
|
|
Index GetOccupiedCount() const {
|
|
|
|
Index count = 0;
|
2020-11-03 21:45:18 +01:00
|
|
|
if (num_starts_ > 0) {
|
|
|
|
const Index num_slots = num_starts_ + kCoeffBits - 1;
|
|
|
|
for (Index i = 0; i < num_slots; ++i) {
|
|
|
|
if (coeff_rows_[i] != 0) {
|
|
|
|
++count;
|
|
|
|
}
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
|
|
|
// ********************************************************************
|
|
|
|
// High-level API
|
|
|
|
|
|
|
|
// Iteratively (a) resets the structure for `num_slots`, (b) attempts
|
|
|
|
// to add the range of inputs, and (c) if unsuccessful, chooses next
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
// hash seed, until either successful or unsuccessful with all the
|
|
|
|
// allowed seeds. Returns true if successful. In that case, use
|
|
|
|
// GetOrdinalSeed() or GetRawSeed() to get the successful seed.
|
|
|
|
//
|
|
|
|
// The allowed sequence of hash seeds is determined by
|
|
|
|
// `starting_ordinal_seed,` the first ordinal seed to be attempted
|
|
|
|
// (see StandardHasher), and `ordinal_seed_mask,` a bit mask (power of
|
|
|
|
// two minus one) for the range of ordinal seeds to consider. The
|
|
|
|
// max number of seeds considered will be ordinal_seed_mask + 1.
|
|
|
|
// For filters we suggest `starting_ordinal_seed` be chosen randomly
|
|
|
|
// or round-robin, to minimize false positive correlations between keys.
|
2020-10-26 04:43:04 +01:00
|
|
|
//
|
|
|
|
// If unsuccessful, how best to continue is going to be application
|
|
|
|
// specific. It should be possible to choose parameters such that
|
|
|
|
// failure is extremely unlikely, using max_seed around 32 to 64.
|
|
|
|
// (TODO: APIs to help choose parameters) One option for fallback in
|
|
|
|
// constructing a filter is to construct a Bloom filter instead.
|
|
|
|
// Increasing num_slots is an option, but should not be used often
|
|
|
|
// unless construction maximum latency is a concern (rather than
|
|
|
|
// average running time of construction). Instead, choose parameters
|
|
|
|
// appropriately and trust that seeds are independent. (Also,
|
|
|
|
// increasing num_slots without changing hash seed would have a
|
|
|
|
// significant correlation in success, rather than independence.)
|
|
|
|
template <typename InputIterator>
|
|
|
|
bool ResetAndFindSeedToSolve(Index num_slots, InputIterator begin,
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
InputIterator end,
|
|
|
|
Seed starting_ordinal_seed = 0U,
|
|
|
|
Seed ordinal_seed_mask = 63U) {
|
|
|
|
// power of 2 minus 1
|
|
|
|
assert((ordinal_seed_mask & (ordinal_seed_mask + 1)) == 0);
|
|
|
|
// starting seed is within mask
|
|
|
|
assert((starting_ordinal_seed & ordinal_seed_mask) ==
|
|
|
|
starting_ordinal_seed);
|
|
|
|
starting_ordinal_seed &= ordinal_seed_mask; // if not debug
|
|
|
|
|
|
|
|
Seed cur_ordinal_seed = starting_ordinal_seed;
|
2020-10-26 04:43:04 +01:00
|
|
|
do {
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
StandardHasher<TypesAndSettings>::SetOrdinalSeed(cur_ordinal_seed);
|
2020-10-26 04:43:04 +01:00
|
|
|
Reset(num_slots);
|
|
|
|
bool success = AddRange(begin, end);
|
|
|
|
if (success) {
|
|
|
|
return true;
|
|
|
|
}
|
Ribbon: major re-work of hashing, seeds, and more (#7635)
Summary:
* Fully optimized StandardHasher, in terms of efficiently generating Start, CoeffRow, and ResultRow from a stock hash value, with sufficient independence between them to have no measurably degraded behavior. (Degraded behavior would be an FP rate higher than explainable by 2^-b and, if using a 32-bit stock hash function, expected stock hash collisions.) Details in code comments.
* Our standard 64-bit and 32-bit hash functions do not exhibit sufficient independence on sequential seeds (for one Ribbon construction attempt to have independent probability from the next). I have worked around this in the Ribbon code by "pre-mixing" "ordinal seeds," sequentially tried and appropriate for storage in persisted metadata, into "raw seeds," ready for application and appropriate for in-memory storage. This way the pre-mixing step (though fast) is only applied on loading or configuring the structure, not on each query or banding add.
* Fix a subtle flaw in which backtracking not clearing ResultRow data could lead to elevated FP rate on keys that were backtracked on and should (for generality) exhibit the same FP rate as novel keys.
* Added a basic test for PhsfQuery and construction algorithms (map or "retrieval structure" rather than set or filter), and made a few trivial related fixes.
* Better random configuration generation in unit tests
* Some other minor cleanup / clarification / etc.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7635
Test Plan: unit tests included
Reviewed By: jay-zhuang
Differential Revision: D24738978
Pulled By: pdillinger
fbshipit-source-id: f9d03599d9e2ca3e30e9d3e7d81cd936b56f76f0
2020-11-08 01:39:14 +01:00
|
|
|
cur_ordinal_seed = (cur_ordinal_seed + 1) & ordinal_seed_mask;
|
|
|
|
} while (cur_ordinal_seed != starting_ordinal_seed);
|
|
|
|
// Reached limit by circling around
|
2020-10-26 04:43:04 +01:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
// ********************************************************************
|
|
|
|
// Static high-level API
|
|
|
|
|
|
|
|
// Based on data from FindOccupancyForSuccessRate in ribbon_test,
|
|
|
|
// returns a number of slots for a given number of entries to add
|
|
|
|
// that should have roughly 95% or better chance of successful
|
|
|
|
// construction per seed. Does NOT do rounding for InterleavedSoln;
|
|
|
|
// call RoundUpNumSlots for that.
|
|
|
|
//
|
|
|
|
// num_to_add should not exceed roughly 2/3rds of the maximum value
|
|
|
|
// of the Index type to avoid overflow.
|
|
|
|
static Index GetNumSlotsFor95PctSuccess(Index num_to_add) {
|
|
|
|
if (num_to_add == 0) {
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
double factor = GetFactorFor95PctSuccess(num_to_add);
|
|
|
|
Index num_slots = static_cast<Index>(num_to_add * factor);
|
|
|
|
assert(num_slots >= num_to_add);
|
|
|
|
return num_slots;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Based on data from FindOccupancyForSuccessRate in ribbon_test,
|
|
|
|
// given a number of entries to add, returns a space overhead factor
|
|
|
|
// (slots divided by num_to_add) that should have roughly 95% or better
|
|
|
|
// chance of successful construction per seed. Does NOT do rounding for
|
|
|
|
// InterleavedSoln; call RoundUpNumSlots for that.
|
|
|
|
//
|
|
|
|
// The reason that num_to_add is needed is that Ribbon filters of a
|
|
|
|
// particular CoeffRow size do not scale infinitely.
|
|
|
|
static double GetFactorFor95PctSuccess(Index num_to_add) {
|
|
|
|
double log2_num_to_add = std::log(num_to_add) * 1.442695;
|
|
|
|
if (kCoeffBits == 64) {
|
|
|
|
if (TypesAndSettings::kUseSmash) {
|
|
|
|
return 1.02 + std::max(log2_num_to_add - 8.5, 0.0) * 0.009;
|
|
|
|
} else {
|
|
|
|
return 1.05 + std::max(log2_num_to_add - 11.0, 0.0) * 0.009;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
// Currently only support 64 and 128
|
|
|
|
assert(kCoeffBits == 128);
|
|
|
|
if (TypesAndSettings::kUseSmash) {
|
|
|
|
return 1.01 + std::max(log2_num_to_add - 10.0, 0.0) * 0.0042;
|
|
|
|
} else {
|
|
|
|
return 1.02 + std::max(log2_num_to_add - 12.0, 0.0) * 0.0042;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
protected:
|
|
|
|
// TODO: explore combining in a struct
|
|
|
|
std::unique_ptr<CoeffRow[]> coeff_rows_;
|
|
|
|
std::unique_ptr<ResultRow[]> result_rows_;
|
|
|
|
// We generally store "starts" instead of slots for speed of GetStart(),
|
|
|
|
// as in StandardHasher.
|
|
|
|
Index num_starts_ = 0;
|
|
|
|
Index num_slots_allocated_ = 0;
|
|
|
|
std::unique_ptr<Index[]> backtrack_;
|
|
|
|
Index backtrack_size_ = 0;
|
|
|
|
};
|
|
|
|
|
|
|
|
// Implements concept SimpleSolutionStorage, mostly for demonstration
|
|
|
|
// purposes. This is "in memory" only because it does not handle byte
|
|
|
|
// ordering issues for serialization.
|
|
|
|
template <class TypesAndSettings>
|
|
|
|
class InMemSimpleSolution {
|
|
|
|
public:
|
|
|
|
IMPORT_RIBBON_TYPES_AND_SETTINGS(TypesAndSettings);
|
|
|
|
|
|
|
|
void PrepareForNumStarts(Index num_starts) {
|
2020-11-03 21:45:18 +01:00
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts == 0) {
|
|
|
|
// Unusual
|
|
|
|
num_starts_ = 0;
|
|
|
|
} else {
|
|
|
|
// Normal
|
|
|
|
const Index num_slots = num_starts + kCoeffBits - 1;
|
|
|
|
assert(num_slots >= kCoeffBits);
|
|
|
|
if (num_slots > num_slots_allocated_) {
|
|
|
|
// Do not need to init the memory
|
|
|
|
solution_rows_.reset(new ResultRow[num_slots]);
|
|
|
|
num_slots_allocated_ = num_slots;
|
|
|
|
}
|
|
|
|
num_starts_ = num_starts;
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
Index GetNumStarts() const { return num_starts_; }
|
|
|
|
|
|
|
|
ResultRow Load(Index slot_num) const { return solution_rows_[slot_num]; }
|
|
|
|
|
|
|
|
void Store(Index slot_num, ResultRow solution_row) {
|
|
|
|
solution_rows_[slot_num] = solution_row;
|
|
|
|
}
|
|
|
|
|
|
|
|
// ********************************************************************
|
|
|
|
// High-level API
|
|
|
|
|
|
|
|
template <typename BandingStorage>
|
2020-11-03 21:45:18 +01:00
|
|
|
void BackSubstFrom(const BandingStorage& bs) {
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && bs.GetNumStarts() == 0) {
|
|
|
|
// Unusual
|
|
|
|
PrepareForNumStarts(0);
|
|
|
|
} else {
|
|
|
|
// Normal
|
|
|
|
SimpleBackSubst(this, bs);
|
|
|
|
}
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
template <typename PhsfQueryHasher>
|
|
|
|
ResultRow PhsfQuery(const Key& input, const PhsfQueryHasher& hasher) {
|
|
|
|
assert(!TypesAndSettings::kIsFilter);
|
2020-11-03 21:45:18 +01:00
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual
|
|
|
|
return 0;
|
|
|
|
} else {
|
|
|
|
// Normal
|
|
|
|
return SimplePhsfQuery(input, hasher, *this);
|
|
|
|
}
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
template <typename FilterQueryHasher>
|
|
|
|
bool FilterQuery(const Key& input, const FilterQueryHasher& hasher) {
|
|
|
|
assert(TypesAndSettings::kIsFilter);
|
2020-11-03 21:45:18 +01:00
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual. Zero starts presumes no keys added -> always false
|
|
|
|
return false;
|
|
|
|
} else {
|
|
|
|
// Normal, or upper_num_columns_ == 0 means "no space for data" and
|
|
|
|
// thus will always return true.
|
|
|
|
return SimpleFilterQuery(input, hasher, *this);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
double ExpectedFpRate() {
|
|
|
|
assert(TypesAndSettings::kIsFilter);
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual, but we don't have FPs if we always return false.
|
|
|
|
return 0.0;
|
|
|
|
}
|
|
|
|
// else Normal
|
|
|
|
|
|
|
|
// Each result (solution) bit (column) cuts FP rate in half
|
|
|
|
return std::pow(0.5, 8U * sizeof(ResultRow));
|
2020-10-26 04:43:04 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
protected:
|
|
|
|
// We generally store "starts" instead of slots for speed of GetStart(),
|
|
|
|
// as in StandardHasher.
|
|
|
|
Index num_starts_ = 0;
|
|
|
|
Index num_slots_allocated_ = 0;
|
|
|
|
std::unique_ptr<ResultRow[]> solution_rows_;
|
|
|
|
};
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
// Implements concept InterleavedSolutionStorage always using little-endian
|
|
|
|
// byte order, so easy for serialization/deserialization. This implementation
|
|
|
|
// fully supports fractional bits per key, where any number of segments
|
|
|
|
// (number of bytes multiple of sizeof(CoeffRow)) can be used with any number
|
|
|
|
// of slots that is a multiple of kCoeffBits.
|
|
|
|
//
|
|
|
|
// The structure is passed an externally allocated/de-allocated byte buffer
|
|
|
|
// that is optionally pre-populated (from storage) for answering queries,
|
|
|
|
// or can be populated by BackSubstFrom.
|
|
|
|
//
|
|
|
|
template <class TypesAndSettings>
|
|
|
|
class SerializableInterleavedSolution {
|
|
|
|
public:
|
|
|
|
IMPORT_RIBBON_TYPES_AND_SETTINGS(TypesAndSettings);
|
|
|
|
|
|
|
|
// Does not take ownership of `data` but uses it (up to `data_len` bytes)
|
|
|
|
// throughout lifetime
|
|
|
|
SerializableInterleavedSolution(char* data, size_t data_len)
|
|
|
|
: data_(data), data_len_(data_len) {}
|
|
|
|
|
|
|
|
void PrepareForNumStarts(Index num_starts) {
|
|
|
|
assert(num_starts == 0 || (num_starts % kCoeffBits == 1));
|
|
|
|
num_starts_ = num_starts;
|
|
|
|
|
|
|
|
InternalConfigure();
|
|
|
|
}
|
|
|
|
|
|
|
|
Index GetNumStarts() const { return num_starts_; }
|
|
|
|
|
|
|
|
Index GetNumBlocks() const {
|
|
|
|
const Index num_slots = num_starts_ + kCoeffBits - 1;
|
|
|
|
return num_slots / kCoeffBits;
|
|
|
|
}
|
|
|
|
|
|
|
|
Index GetUpperNumColumns() const { return upper_num_columns_; }
|
|
|
|
|
|
|
|
Index GetUpperStartBlock() const { return upper_start_block_; }
|
|
|
|
|
|
|
|
Index GetNumSegments() const {
|
|
|
|
return static_cast<Index>(data_len_ / sizeof(CoeffRow));
|
|
|
|
}
|
|
|
|
|
|
|
|
CoeffRow LoadSegment(Index segment_num) const {
|
|
|
|
assert(data_ != nullptr); // suppress clang analyzer report
|
|
|
|
return DecodeFixedGeneric<CoeffRow>(data_ + segment_num * sizeof(CoeffRow));
|
|
|
|
}
|
|
|
|
void StoreSegment(Index segment_num, CoeffRow val) {
|
|
|
|
assert(data_ != nullptr); // suppress clang analyzer report
|
|
|
|
EncodeFixedGeneric(data_ + segment_num * sizeof(CoeffRow), val);
|
|
|
|
}
|
Add prefetching (batched MultiGet) for experimental Ribbon filter (#7889)
Summary:
Adds support for prefetching data in Ribbon queries,
which especially optimizes batched Ribbon queries for MultiGet
(~222ns/key to ~97ns/key) but also single key queries on cold memory
(~333ns to ~226ns) because many queries span more than one cache line.
This required some refactoring of the query algorithm, and there
does not appear to be a noticeable regression in "hot memory" query
times (perhaps from 48ns to 50ns).
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7889
Test Plan:
existing unit tests, plus performance validation with
filter_bench:
Each data point is the best of two runs. I saturated the machine
CPUs with other filter_bench runs in the background.
Before:
$ ./filter_bench -impl=3 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 125.86
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
Prelim FP rate %: 0.951827
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 48.0111
Batched, prepared net ns/op: 222.384
Batched, unprepared net ns/op: 343.908
Skewed 50% in 1% net ns/op: 252.916
Skewed 80% in 20% net ns/op: 320.579
Random filter net ns/op: 332.957
After:
$ ./filter_bench -impl=3 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 128.117
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
Prelim FP rate %: 0.951827
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 49.8812
Batched, prepared net ns/op: 97.1514
Batched, unprepared net ns/op: 222.025
Skewed 50% in 1% net ns/op: 197.48
Skewed 80% in 20% net ns/op: 212.457
Random filter net ns/op: 226.464
Bloom comparison, for reference:
$ ./filter_bench -impl=2 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 35.3042
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
Prelim FP rate %: 0.965327
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 9.09931
Batched, prepared net ns/op: 34.21
Batched, unprepared net ns/op: 88.8564
Skewed 50% in 1% net ns/op: 139.75
Skewed 80% in 20% net ns/op: 181.264
Random filter net ns/op: 173.88
Reviewed By: jay-zhuang
Differential Revision: D26378710
Pulled By: pdillinger
fbshipit-source-id: 058428967c55ed763698284cd3b4bbe3351b6e69
2021-02-11 06:03:35 +01:00
|
|
|
void PrefetchSegmentRange(Index begin_segment_num,
|
|
|
|
Index end_segment_num) const {
|
|
|
|
if (end_segment_num == begin_segment_num) {
|
|
|
|
// Nothing to do
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
char* cur = data_ + begin_segment_num * sizeof(CoeffRow);
|
|
|
|
char* last = data_ + (end_segment_num - 1) * sizeof(CoeffRow);
|
|
|
|
while (cur < last) {
|
|
|
|
PREFETCH(cur, 0 /* rw */, 1 /* locality */);
|
|
|
|
cur += CACHE_LINE_SIZE;
|
|
|
|
}
|
|
|
|
PREFETCH(last, 0 /* rw */, 1 /* locality */);
|
|
|
|
}
|
2020-11-03 21:45:18 +01:00
|
|
|
|
|
|
|
// ********************************************************************
|
|
|
|
// High-level API
|
|
|
|
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
void ConfigureForNumBlocks(Index num_blocks) {
|
|
|
|
if (num_blocks == 0) {
|
|
|
|
PrepareForNumStarts(0);
|
|
|
|
} else {
|
|
|
|
PrepareForNumStarts(num_blocks * kCoeffBits - kCoeffBits + 1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void ConfigureForNumSlots(Index num_slots) {
|
|
|
|
assert(num_slots % kCoeffBits == 0);
|
|
|
|
ConfigureForNumBlocks(num_slots / kCoeffBits);
|
|
|
|
}
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
template <typename BandingStorage>
|
|
|
|
void BackSubstFrom(const BandingStorage& bs) {
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && bs.GetNumStarts() == 0) {
|
|
|
|
// Unusual
|
|
|
|
PrepareForNumStarts(0);
|
|
|
|
} else {
|
|
|
|
// Normal
|
|
|
|
InterleavedBackSubst(this, bs);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
template <typename PhsfQueryHasher>
|
|
|
|
ResultRow PhsfQuery(const Key& input, const PhsfQueryHasher& hasher) {
|
|
|
|
assert(!TypesAndSettings::kIsFilter);
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual
|
|
|
|
return 0;
|
|
|
|
} else {
|
|
|
|
// Normal
|
Add prefetching (batched MultiGet) for experimental Ribbon filter (#7889)
Summary:
Adds support for prefetching data in Ribbon queries,
which especially optimizes batched Ribbon queries for MultiGet
(~222ns/key to ~97ns/key) but also single key queries on cold memory
(~333ns to ~226ns) because many queries span more than one cache line.
This required some refactoring of the query algorithm, and there
does not appear to be a noticeable regression in "hot memory" query
times (perhaps from 48ns to 50ns).
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7889
Test Plan:
existing unit tests, plus performance validation with
filter_bench:
Each data point is the best of two runs. I saturated the machine
CPUs with other filter_bench runs in the background.
Before:
$ ./filter_bench -impl=3 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 125.86
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
Prelim FP rate %: 0.951827
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 48.0111
Batched, prepared net ns/op: 222.384
Batched, unprepared net ns/op: 343.908
Skewed 50% in 1% net ns/op: 252.916
Skewed 80% in 20% net ns/op: 320.579
Random filter net ns/op: 332.957
After:
$ ./filter_bench -impl=3 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 128.117
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
Prelim FP rate %: 0.951827
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 49.8812
Batched, prepared net ns/op: 97.1514
Batched, unprepared net ns/op: 222.025
Skewed 50% in 1% net ns/op: 197.48
Skewed 80% in 20% net ns/op: 212.457
Random filter net ns/op: 226.464
Bloom comparison, for reference:
$ ./filter_bench -impl=2 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 35.3042
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
Prelim FP rate %: 0.965327
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 9.09931
Batched, prepared net ns/op: 34.21
Batched, unprepared net ns/op: 88.8564
Skewed 50% in 1% net ns/op: 139.75
Skewed 80% in 20% net ns/op: 181.264
Random filter net ns/op: 173.88
Reviewed By: jay-zhuang
Differential Revision: D26378710
Pulled By: pdillinger
fbshipit-source-id: 058428967c55ed763698284cd3b4bbe3351b6e69
2021-02-11 06:03:35 +01:00
|
|
|
// NOTE: not using a struct to encourage compiler optimization
|
|
|
|
Hash hash;
|
|
|
|
Index segment_num;
|
|
|
|
Index num_columns;
|
|
|
|
Index start_bit;
|
|
|
|
InterleavedPrepareQuery(input, hasher, *this, &hash, &segment_num,
|
|
|
|
&num_columns, &start_bit);
|
|
|
|
return InterleavedPhsfQuery(hash, segment_num, num_columns, start_bit,
|
|
|
|
hasher, *this);
|
2020-11-03 21:45:18 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
template <typename FilterQueryHasher>
|
|
|
|
bool FilterQuery(const Key& input, const FilterQueryHasher& hasher) {
|
|
|
|
assert(TypesAndSettings::kIsFilter);
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual. Zero starts presumes no keys added -> always false
|
|
|
|
return false;
|
|
|
|
} else {
|
|
|
|
// Normal, or upper_num_columns_ == 0 means "no space for data" and
|
|
|
|
// thus will always return true.
|
Add prefetching (batched MultiGet) for experimental Ribbon filter (#7889)
Summary:
Adds support for prefetching data in Ribbon queries,
which especially optimizes batched Ribbon queries for MultiGet
(~222ns/key to ~97ns/key) but also single key queries on cold memory
(~333ns to ~226ns) because many queries span more than one cache line.
This required some refactoring of the query algorithm, and there
does not appear to be a noticeable regression in "hot memory" query
times (perhaps from 48ns to 50ns).
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7889
Test Plan:
existing unit tests, plus performance validation with
filter_bench:
Each data point is the best of two runs. I saturated the machine
CPUs with other filter_bench runs in the background.
Before:
$ ./filter_bench -impl=3 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 125.86
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
Prelim FP rate %: 0.951827
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 48.0111
Batched, prepared net ns/op: 222.384
Batched, unprepared net ns/op: 343.908
Skewed 50% in 1% net ns/op: 252.916
Skewed 80% in 20% net ns/op: 320.579
Random filter net ns/op: 332.957
After:
$ ./filter_bench -impl=3 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 128.117
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
Prelim FP rate %: 0.951827
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 49.8812
Batched, prepared net ns/op: 97.1514
Batched, unprepared net ns/op: 222.025
Skewed 50% in 1% net ns/op: 197.48
Skewed 80% in 20% net ns/op: 212.457
Random filter net ns/op: 226.464
Bloom comparison, for reference:
$ ./filter_bench -impl=2 -m_keys_total_max=200 -average_keys_per_filter=100000 -m_queries=50
WARNING: Assertions are enabled; benchmarks unnecessarily slow
Building...
Build avg ns/key: 35.3042
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
Prelim FP rate %: 0.965327
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 9.09931
Batched, prepared net ns/op: 34.21
Batched, unprepared net ns/op: 88.8564
Skewed 50% in 1% net ns/op: 139.75
Skewed 80% in 20% net ns/op: 181.264
Random filter net ns/op: 173.88
Reviewed By: jay-zhuang
Differential Revision: D26378710
Pulled By: pdillinger
fbshipit-source-id: 058428967c55ed763698284cd3b4bbe3351b6e69
2021-02-11 06:03:35 +01:00
|
|
|
// NOTE: not using a struct to encourage compiler optimization
|
|
|
|
Hash hash;
|
|
|
|
Index segment_num;
|
|
|
|
Index num_columns;
|
|
|
|
Index start_bit;
|
|
|
|
InterleavedPrepareQuery(input, hasher, *this, &hash, &segment_num,
|
|
|
|
&num_columns, &start_bit);
|
|
|
|
return InterleavedFilterQuery(hash, segment_num, num_columns, start_bit,
|
|
|
|
hasher, *this);
|
2020-11-03 21:45:18 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
double ExpectedFpRate() {
|
|
|
|
assert(TypesAndSettings::kIsFilter);
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts && num_starts_ == 0) {
|
|
|
|
// Unusual. Zero starts presumes no keys added -> always false
|
|
|
|
return 0.0;
|
|
|
|
}
|
|
|
|
// else Normal
|
|
|
|
|
|
|
|
// Note: Ignoring smash setting; still close enough in that case
|
|
|
|
double lower_portion =
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
(upper_start_block_ * 1.0 * kCoeffBits) / num_starts_;
|
2020-11-03 21:45:18 +01:00
|
|
|
|
|
|
|
// Each result (solution) bit (column) cuts FP rate in half. Weight that
|
|
|
|
// for upper and lower number of bits (columns).
|
|
|
|
return lower_portion * std::pow(0.5, upper_num_columns_ - 1) +
|
|
|
|
(1.0 - lower_portion) * std::pow(0.5, upper_num_columns_);
|
|
|
|
}
|
|
|
|
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
// ********************************************************************
|
|
|
|
// Static high-level API
|
|
|
|
|
|
|
|
// Round up to a number of slots supported by this structure. Note that
|
|
|
|
// this needs to be must be taken into account for the banding if this
|
|
|
|
// solution layout/storage is to be used.
|
|
|
|
static Index RoundUpNumSlots(Index num_slots) {
|
|
|
|
// Must be multiple of kCoeffBits
|
|
|
|
Index corrected = (num_slots + kCoeffBits - 1) / kCoeffBits * kCoeffBits;
|
|
|
|
|
|
|
|
// Do not use num_starts==1 unless kUseSmash, because the hashing
|
|
|
|
// might not be equipped for stacking up so many entries on a
|
|
|
|
// single start location.
|
|
|
|
if (!TypesAndSettings::kUseSmash && corrected == kCoeffBits) {
|
|
|
|
corrected += kCoeffBits;
|
|
|
|
}
|
|
|
|
return corrected;
|
|
|
|
}
|
|
|
|
|
Support optimize_filters_for_memory for Ribbon filter (#7774)
Summary:
Primarily this change refactors the optimize_filters_for_memory
code for Bloom filters, based on malloc_usable_size, to also work for
Ribbon filters.
This change also replaces the somewhat slow but general
BuiltinFilterBitsBuilder::ApproximateNumEntries with
implementation-specific versions for Ribbon (new) and Legacy Bloom
(based on a recently deleted version). The reason is to emphasize
speed in ApproximateNumEntries rather than 100% accuracy.
Justification: ApproximateNumEntries (formerly CalculateNumEntry) is
only used by RocksDB for range-partitioned filters, called each time we
start to construct one. (In theory, it should be possible to reuse the
estimate, but the abstractions provided by FilterPolicy don't really
make that workable.) But this is only used as a heuristic estimate for
hitting a desired partitioned filter size because of alignment to data
blocks, which have various numbers of unique keys or prefixes. The two
factors lead us to prioritize reasonable speed over 100% accuracy.
optimize_filters_for_memory adds extra complication, because precisely
calculating num_entries for some allowed number of bytes depends on state
with optimize_filters_for_memory enabled. And the allocator-agnostic
implementation of optimize_filters_for_memory, using malloc_usable_size,
means we would have to actually allocate memory, many times, just to
precisely determine how many entries (keys) could be added and stay below
some size budget, for the current state. (In a draft, I got this
working, and then realized the balance of speed vs. accuracy was all
wrong.)
So related to that, I have made CalculateSpace, an internal-only API
only used for testing, non-authoritative also if
optimize_filters_for_memory is enabled. This simplifies some code.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7774
Test Plan:
unit test updated, and for FilterSize test, range of tested
values is greatly expanded (still super fast)
Also tested `db_bench -benchmarks=fillrandom,stats -bloom_bits=10 -num=1000000 -partition_index_and_filters -format_version=5 [-optimize_filters_for_memory] [-use_ribbon_filter]` with temporary debug output of generated filter sizes.
Bloom+optimize_filters_for_memory:
1 Filter size: 197 (224 in memory)
134 Filter size: 3525 (3584 in memory)
107 Filter size: 4037 (4096 in memory)
Total on disk: 904,506
Total in memory: 918,752
Ribbon+optimize_filters_for_memory:
1 Filter size: 3061 (3072 in memory)
110 Filter size: 3573 (3584 in memory)
58 Filter size: 4085 (4096 in memory)
Total on disk: 633,021 (-30.0%)
Total in memory: 634,880 (-30.9%)
Bloom (no offm):
1 Filter size: 261 (320 in memory)
1 Filter size: 3333 (3584 in memory)
240 Filter size: 3717 (4096 in memory)
Total on disk: 895,674 (-1% on disk vs. +offm; known tolerable overhead of offm)
Total in memory: 986,944 (+7.4% vs. +offm)
Ribbon (no offm):
1 Filter size: 2949 (3072 in memory)
1 Filter size: 3381 (3584 in memory)
167 Filter size: 3701 (4096 in memory)
Total on disk: 624,397 (-30.3% vs. Bloom)
Total in memory: 690,688 (-30.0% vs. Bloom)
Note that optimize_filters_for_memory is even more effective for Ribbon filter than for cache-local Bloom, because it can close the unused memory gap even tighter than Bloom filter, because of 16 byte increments for Ribbon vs. 64 byte increments for Bloom.
Reviewed By: jay-zhuang
Differential Revision: D25592970
Pulled By: pdillinger
fbshipit-source-id: 606fdaa025bb790d7e9c21601e8ea86e10541912
2020-12-18 23:29:48 +01:00
|
|
|
// Round down to a number of slots supported by this structure. Note that
|
|
|
|
// this needs to be must be taken into account for the banding if this
|
|
|
|
// solution layout/storage is to be used.
|
|
|
|
static Index RoundDownNumSlots(Index num_slots) {
|
|
|
|
// Must be multiple of kCoeffBits
|
|
|
|
Index corrected = num_slots / kCoeffBits * kCoeffBits;
|
|
|
|
|
|
|
|
// Do not use num_starts==1 unless kUseSmash, because the hashing
|
|
|
|
// might not be equipped for stacking up so many entries on a
|
|
|
|
// single start location.
|
|
|
|
if (!TypesAndSettings::kUseSmash && corrected == kCoeffBits) {
|
|
|
|
corrected = 0;
|
|
|
|
}
|
|
|
|
return corrected;
|
|
|
|
}
|
|
|
|
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
// Compute the number of bytes for a given number of slots and desired
|
|
|
|
// FP rate. Since desired FP rate might not be exactly achievable,
|
|
|
|
// rounding_bias32==0 means to always round toward lower FP rate
|
|
|
|
// than desired (more bytes); rounding_bias32==max uint32_t means always
|
|
|
|
// round toward higher FP rate than desired (fewer bytes); other values
|
|
|
|
// act as a proportional threshold or bias between the two.
|
|
|
|
static size_t GetBytesForFpRate(Index num_slots, double desired_fp_rate,
|
|
|
|
uint32_t rounding_bias32) {
|
|
|
|
return InternalGetBytesForFpRate(num_slots, desired_fp_rate,
|
|
|
|
1.0 / desired_fp_rate, rounding_bias32);
|
|
|
|
}
|
|
|
|
|
|
|
|
// The same, but specifying desired accuracy as 1.0 / FP rate, or
|
|
|
|
// one_in_fp_rate. E.g. desired_one_in_fp_rate=100 means 1% FP rate.
|
|
|
|
static size_t GetBytesForOneInFpRate(Index num_slots,
|
|
|
|
double desired_one_in_fp_rate,
|
|
|
|
uint32_t rounding_bias32) {
|
|
|
|
return InternalGetBytesForFpRate(num_slots, 1.0 / desired_one_in_fp_rate,
|
|
|
|
desired_one_in_fp_rate, rounding_bias32);
|
|
|
|
}
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
protected:
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
static size_t InternalGetBytesForFpRate(Index num_slots,
|
|
|
|
double desired_fp_rate,
|
|
|
|
double desired_one_in_fp_rate,
|
|
|
|
uint32_t rounding_bias32) {
|
|
|
|
assert(TypesAndSettings::kIsFilter);
|
Support optimize_filters_for_memory for Ribbon filter (#7774)
Summary:
Primarily this change refactors the optimize_filters_for_memory
code for Bloom filters, based on malloc_usable_size, to also work for
Ribbon filters.
This change also replaces the somewhat slow but general
BuiltinFilterBitsBuilder::ApproximateNumEntries with
implementation-specific versions for Ribbon (new) and Legacy Bloom
(based on a recently deleted version). The reason is to emphasize
speed in ApproximateNumEntries rather than 100% accuracy.
Justification: ApproximateNumEntries (formerly CalculateNumEntry) is
only used by RocksDB for range-partitioned filters, called each time we
start to construct one. (In theory, it should be possible to reuse the
estimate, but the abstractions provided by FilterPolicy don't really
make that workable.) But this is only used as a heuristic estimate for
hitting a desired partitioned filter size because of alignment to data
blocks, which have various numbers of unique keys or prefixes. The two
factors lead us to prioritize reasonable speed over 100% accuracy.
optimize_filters_for_memory adds extra complication, because precisely
calculating num_entries for some allowed number of bytes depends on state
with optimize_filters_for_memory enabled. And the allocator-agnostic
implementation of optimize_filters_for_memory, using malloc_usable_size,
means we would have to actually allocate memory, many times, just to
precisely determine how many entries (keys) could be added and stay below
some size budget, for the current state. (In a draft, I got this
working, and then realized the balance of speed vs. accuracy was all
wrong.)
So related to that, I have made CalculateSpace, an internal-only API
only used for testing, non-authoritative also if
optimize_filters_for_memory is enabled. This simplifies some code.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7774
Test Plan:
unit test updated, and for FilterSize test, range of tested
values is greatly expanded (still super fast)
Also tested `db_bench -benchmarks=fillrandom,stats -bloom_bits=10 -num=1000000 -partition_index_and_filters -format_version=5 [-optimize_filters_for_memory] [-use_ribbon_filter]` with temporary debug output of generated filter sizes.
Bloom+optimize_filters_for_memory:
1 Filter size: 197 (224 in memory)
134 Filter size: 3525 (3584 in memory)
107 Filter size: 4037 (4096 in memory)
Total on disk: 904,506
Total in memory: 918,752
Ribbon+optimize_filters_for_memory:
1 Filter size: 3061 (3072 in memory)
110 Filter size: 3573 (3584 in memory)
58 Filter size: 4085 (4096 in memory)
Total on disk: 633,021 (-30.0%)
Total in memory: 634,880 (-30.9%)
Bloom (no offm):
1 Filter size: 261 (320 in memory)
1 Filter size: 3333 (3584 in memory)
240 Filter size: 3717 (4096 in memory)
Total on disk: 895,674 (-1% on disk vs. +offm; known tolerable overhead of offm)
Total in memory: 986,944 (+7.4% vs. +offm)
Ribbon (no offm):
1 Filter size: 2949 (3072 in memory)
1 Filter size: 3381 (3584 in memory)
167 Filter size: 3701 (4096 in memory)
Total on disk: 624,397 (-30.3% vs. Bloom)
Total in memory: 690,688 (-30.0% vs. Bloom)
Note that optimize_filters_for_memory is even more effective for Ribbon filter than for cache-local Bloom, because it can close the unused memory gap even tighter than Bloom filter, because of 16 byte increments for Ribbon vs. 64 byte increments for Bloom.
Reviewed By: jay-zhuang
Differential Revision: D25592970
Pulled By: pdillinger
fbshipit-source-id: 606fdaa025bb790d7e9c21601e8ea86e10541912
2020-12-18 23:29:48 +01:00
|
|
|
if (TypesAndSettings::kAllowZeroStarts) {
|
|
|
|
if (num_slots == 0) {
|
|
|
|
// Unusual. Zero starts presumes no keys added -> always false (no FPs)
|
|
|
|
return 0U;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
assert(num_slots > 0);
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
}
|
|
|
|
// Must be rounded up already.
|
|
|
|
assert(RoundUpNumSlots(num_slots) == num_slots);
|
|
|
|
|
|
|
|
if (desired_one_in_fp_rate > 1.0 && desired_fp_rate < 1.0) {
|
|
|
|
// Typical: less than 100% FP rate
|
|
|
|
if (desired_one_in_fp_rate <= static_cast<ResultRow>(-1)) {
|
|
|
|
// Typical: Less than maximum result row entropy
|
|
|
|
ResultRow rounded = static_cast<ResultRow>(desired_one_in_fp_rate);
|
|
|
|
int lower_columns = FloorLog2(rounded);
|
|
|
|
double lower_columns_fp_rate = std::pow(2.0, -lower_columns);
|
|
|
|
double upper_columns_fp_rate = std::pow(2.0, -(lower_columns + 1));
|
|
|
|
// Floating point don't let me down!
|
|
|
|
assert(lower_columns_fp_rate >= desired_fp_rate);
|
|
|
|
assert(upper_columns_fp_rate <= desired_fp_rate);
|
|
|
|
|
|
|
|
double lower_portion = (desired_fp_rate - upper_columns_fp_rate) /
|
|
|
|
(lower_columns_fp_rate - upper_columns_fp_rate);
|
|
|
|
// Floating point don't let me down!
|
|
|
|
assert(lower_portion >= 0.0);
|
|
|
|
assert(lower_portion <= 1.0);
|
|
|
|
|
|
|
|
double rounding_bias = (rounding_bias32 + 0.5) / double{0x100000000};
|
|
|
|
assert(rounding_bias > 0.0);
|
|
|
|
assert(rounding_bias < 1.0);
|
|
|
|
|
|
|
|
// Note: Ignoring smash setting; still close enough in that case
|
|
|
|
Index num_starts = num_slots - kCoeffBits + 1;
|
|
|
|
// Lower upper_start_block means lower FP rate (higher accuracy)
|
|
|
|
Index upper_start_block = static_cast<Index>(
|
|
|
|
(lower_portion * num_starts + rounding_bias) / kCoeffBits);
|
|
|
|
Index num_blocks = num_slots / kCoeffBits;
|
|
|
|
assert(upper_start_block < num_blocks);
|
|
|
|
|
|
|
|
// Start by assuming all blocks use lower number of columns
|
|
|
|
Index num_segments = num_blocks * static_cast<Index>(lower_columns);
|
|
|
|
// Correct by 1 each for blocks using upper number of columns
|
|
|
|
num_segments += (num_blocks - upper_start_block);
|
|
|
|
// Total bytes
|
|
|
|
return num_segments * sizeof(CoeffRow);
|
|
|
|
} else {
|
|
|
|
// one_in_fp_rate too big, thus requested FP rate is smaller than
|
|
|
|
// supported. Use max number of columns for minimum supported FP rate.
|
|
|
|
return num_slots * sizeof(ResultRow);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
// Effectively asking for 100% FP rate, or NaN etc.
|
|
|
|
if (TypesAndSettings::kAllowZeroStarts) {
|
|
|
|
// Zero segments
|
|
|
|
return 0U;
|
|
|
|
} else {
|
|
|
|
// One segment (minimum size, maximizing FP rate)
|
|
|
|
return sizeof(CoeffRow);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-11-03 21:45:18 +01:00
|
|
|
void InternalConfigure() {
|
|
|
|
const Index num_blocks = GetNumBlocks();
|
|
|
|
Index num_segments = GetNumSegments();
|
|
|
|
|
|
|
|
if (num_blocks == 0) {
|
|
|
|
// Exceptional
|
|
|
|
upper_num_columns_ = 0;
|
|
|
|
upper_start_block_ = 0;
|
|
|
|
} else {
|
|
|
|
// Normal
|
|
|
|
upper_num_columns_ =
|
|
|
|
(num_segments + /*round up*/ num_blocks - 1) / num_blocks;
|
|
|
|
upper_start_block_ = upper_num_columns_ * num_blocks - num_segments;
|
|
|
|
// Unless that's more columns than supported by ResultRow data type
|
|
|
|
if (upper_num_columns_ > 8U * sizeof(ResultRow)) {
|
|
|
|
// Use maximum columns (there will be space unused)
|
|
|
|
upper_num_columns_ = static_cast<Index>(8U * sizeof(ResultRow));
|
|
|
|
upper_start_block_ = 0;
|
|
|
|
num_segments = num_blocks * upper_num_columns_;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// Update data_len_ for correct rounding and/or unused space
|
|
|
|
// NOTE: unused space stays gone if we PrepareForNumStarts again.
|
|
|
|
// We are prioritizing minimizing the number of fields over making
|
|
|
|
// the "unusued space" feature work well.
|
|
|
|
data_len_ = num_segments * sizeof(CoeffRow);
|
|
|
|
}
|
|
|
|
|
Experimental (production candidate) SST schema for Ribbon filter (#7658)
Summary:
Added experimental public API for Ribbon filter:
NewExperimentalRibbonFilterPolicy(). This experimental API will
take a "Bloom equivalent" bits per key, and configure the Ribbon
filter for the same FP rate as Bloom would have but ~30% space
savings. (Note: optimize_filters_for_memory is not yet implemented
for Ribbon filter. That can be added with no effect on schema.)
Internally, the Ribbon filter is configured using a "one_in_fp_rate"
value, which is 1 over desired FP rate. For example, use 100 for 1%
FP rate. I'm expecting this will be used in the future for configuring
Bloom-like filters, as I expect people to more commonly hold constant
the filter accuracy and change the space vs. time trade-off, rather than
hold constant the space (per key) and change the accuracy vs. time
trade-off, though we might make that available.
### Benchmarking
```
$ ./filter_bench -impl=2 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 34.1341
Number of filters: 1993
Total size (MB): 238.488
Reported total allocated memory (MB): 262.875
Reported internal fragmentation: 10.2255%
Bits/key stored: 10.0029
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 18.7508
Random filter net ns/op: 258.246
Average FP rate %: 0.968672
----------------------------
Done. (For more info, run with -legend or -help.)
$ ./filter_bench -impl=3 -quick -m_keys_total_max=200 -average_keys_per_filter=100000 -net_includes_hashing
Building...
Build avg ns/key: 130.851
Number of filters: 1993
Total size (MB): 168.166
Reported total allocated memory (MB): 183.211
Reported internal fragmentation: 8.94626%
Bits/key stored: 7.05341
----------------------------
Mixed inside/outside queries...
Single filter net ns/op: 58.4523
Random filter net ns/op: 363.717
Average FP rate %: 0.952978
----------------------------
Done. (For more info, run with -legend or -help.)
```
168.166 / 238.488 = 0.705 -> 29.5% space reduction
130.851 / 34.1341 = 3.83x construction time for this Ribbon filter vs. lastest Bloom filter (could make that as little as about 2.5x for less space reduction)
### Working around a hashing "flaw"
bloom_test discovered a flaw in the simple hashing applied in
StandardHasher when num_starts == 1 (num_slots == 128), showing an
excessively high FP rate. The problem is that when many entries, on the
order of number of hash bits or kCoeffBits, are associated with the same
start location, the correlation between the CoeffRow and ResultRow (for
efficiency) can lead to a solution that is "universal," or nearly so, for
entries mapping to that start location. (Normally, variance in start
location breaks the effective association between CoeffRow and
ResultRow; the same value for CoeffRow is effectively different if start
locations are different.) Without kUseSmash and with num_starts > 1 (thus
num_starts ~= num_slots), this flaw should be completely irrelevant. Even
with 10M slots, the chances of a single slot having just 16 (or more)
entries map to it--not enough to cause an FP problem, which would be local
to that slot if it happened--is 1 in millions. This spreadsheet formula
shows that: =1/(10000000*(1 - POISSON(15, 1, TRUE)))
As kUseSmash==false (the setting for Standard128RibbonBitsBuilder) is
intended for CPU efficiency of filters with many more entries/slots than
kCoeffBits, a very reasonable work-around is to disallow num_starts==1
when !kUseSmash, by making the minimum non-zero number of slots
2*kCoeffBits. This is the work-around I've applied. This also means that
the new Ribbon filter schema (Standard128RibbonBitsBuilder) is not
space-efficient for less than a few hundred entries. Because of this, I
have made it fall back on constructing a Bloom filter, under existing
schema, when that is more space efficient for small filters. (We can
change this in the future if we want.)
TODO: better unit tests for this case in ribbon_test, and probably
update StandardHasher for kUseSmash case so that it can scale nicely to
small filters.
### Other related changes
* Add Ribbon filter to stress/crash test
* Add Ribbon filter to filter_bench as -impl=3
* Add option string support, as in "filter_policy=experimental_ribbon:5.678;"
where 5.678 is the Bloom equivalent bits per key.
* Rename internal mode BloomFilterPolicy::kAuto to kAutoBloom
* Add a general BuiltinFilterBitsBuilder::CalculateNumEntry based on
binary searching CalculateSpace (inefficient), so that subclasses
(especially experimental ones) don't have to provide an efficient
implementation inverting CalculateSpace.
* Minor refactor FastLocalBloomBitsBuilder for new base class
XXH3pFilterBitsBuilder shared with new Standard128RibbonBitsBuilder,
which allows the latter to fall back on Bloom construction in some
extreme cases.
* Mostly updated bloom_test for Ribbon filter, though a test like
FullBloomTest::Schema is a next TODO to ensure schema stability
(in case this becomes production-ready schema as it is).
* Add some APIs to ribbon_impl.h for configuring Ribbon filters.
Although these are reasonably covered by bloom_test, TODO more unit
tests in ribbon_test
* Added a "tool" FindOccupancyForSuccessRate to ribbon_test to get data
for constructing the linear approximations in GetNumSlotsFor95PctSuccess.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/7658
Test Plan:
Some unit tests updated but other testing is left TODO. This
is considered experimental but laying down schema compatibility as early
as possible in case it proves production-quality. Also tested in
stress/crash test.
Reviewed By: jay-zhuang
Differential Revision: D24899349
Pulled By: pdillinger
fbshipit-source-id: 9715f3e6371c959d923aea8077c9423c7a9f82b8
2020-11-13 05:45:02 +01:00
|
|
|
char* const data_;
|
|
|
|
size_t data_len_;
|
2020-11-03 21:45:18 +01:00
|
|
|
Index num_starts_ = 0;
|
|
|
|
Index upper_num_columns_ = 0;
|
|
|
|
Index upper_start_block_ = 0;
|
|
|
|
};
|
|
|
|
|
2020-10-26 04:43:04 +01:00
|
|
|
} // namespace ribbon
|
|
|
|
|
|
|
|
} // namespace ROCKSDB_NAMESPACE
|
|
|
|
|
|
|
|
// For convenience working with templates
|
|
|
|
#define IMPORT_RIBBON_IMPL_TYPES(TypesAndSettings) \
|
|
|
|
using Hasher = ROCKSDB_NAMESPACE::ribbon::StandardHasher<TypesAndSettings>; \
|
|
|
|
using Banding = \
|
|
|
|
ROCKSDB_NAMESPACE::ribbon::StandardBanding<TypesAndSettings>; \
|
|
|
|
using SimpleSoln = \
|
|
|
|
ROCKSDB_NAMESPACE::ribbon::InMemSimpleSolution<TypesAndSettings>; \
|
2020-11-03 21:45:18 +01:00
|
|
|
using InterleavedSoln = \
|
|
|
|
ROCKSDB_NAMESPACE::ribbon::SerializableInterleavedSolution< \
|
|
|
|
TypesAndSettings>; \
|
|
|
|
static_assert(sizeof(Hasher) + sizeof(Banding) + sizeof(SimpleSoln) + \
|
|
|
|
sizeof(InterleavedSoln) > \
|
|
|
|
0, \
|
2020-10-26 04:43:04 +01:00
|
|
|
"avoid unused warnings, semicolon expected after macro call")
|