There is big array of entries having the following type:
typedef struct {
int value;
int mask;
int otherData;
} Entry;
I'd like to find an entry in this array according to provided int key;
as fast as posible. The entry is required to ensure that (key & mask) == value
.
What will be the best way for such array organization and what is the corresponding algorithm processing it?
Edit: There is no restrictions on the array organization; it is static and can be prepared before lookup. The value
and mask
may have arbitrary values.
Edit2: value
and mask
may have arbitrary values, but number of entries in the array is about 10000. So, certain "paterns" can be calculated in advance.
The number of lookups is big.
If you're wearing a face mask or potentially other face coverings, Face ID with a mask can analyze the unique characteristics around your eyes. When using Face ID with a mask, you can still use Face ID to authenticate apps, unlock your iPhone, and use Apple Pay.
An app for iOS and Android devicesIt detects faces as people walk past the tablet's camera, and determines if they are wearing a mask (properly) or not. It provides visual feedback to encourage compliance.
Loosely woven cloth products provide the least protection, layered finely woven products offer more protection, well-fitting disposable surgical masks and KN95s offer even more protection, and well-fitting NIOSH-approved respirators (including N95s) offer the highest level of protection.
Each bit is independent, so in a preprocessing phase[*] you could classify each entry 32 (or however big your int
is) times. Each classification stores 2 sets: those which match at that bit when key
is 0 and those which match when key
is 1.
That is, if value == 1 and mask == 0 at that bit, then that classification doesn't store that entry at all, since it doesn't match any value of key
(in fact, no matter what scheme you use, such entries should be removed during any preprocessing stage, so no classification should store an entry if even one bit is like this). If both 0, store into both sets. Otherwise store into one of the two sets.
Then, given your key, you want to find a fast intersection of 32 sets.
Depending on the size of the original array, it may be that the best way to store each set is a giant bit array indicating whether each entry in the array is in the set or not. Then finding the intersection can be done a word at a time - &
together 32 words, one from each bit array. If the result is 0, keep going. If the result is non-0, you have a match, and the bit that's set in the result tells you which entry is the match. This is still linear in the size of the array, of course, and in fact you're doing 31 &
operations to check 32 entries for a match, which is about the same as the simple linear search through the original array. But there's less comparison and branching, and the data you're looking at is more compressed, so you might get better performance.
Or there might be a better way to do the intersection.
If keys tend to be re-used then you should cache the results of the lookup in a map from keys to entries. If the number of possible keys is reasonably small (that is, if significantly less than 2^32 keys are possible inputs, and/or you have a lot of memory available), then your preprocessing phase could just be:
[*] Without any preprocessing, obviously all you can do is check every array member until either you find a match or else you've checked everything.
Since you don't have extra information (for example, that the array is sorted) you need a linear search - traverse the array and check the condition - pseudocode:
for( size_t index = 0; index < arraySize; index++ ) {
if( ( array[index].mask & key ) == array[index].value ) ) {
return index;
}
}
return -1;
If you instead had a map of keys to Entries, then this would be really easy.
If your array were sorted by key, then you could do a lexicographic binary search with some small effort. [actually, maybe not!]
As it is, you're just going to have to traverse the array until you find what you're looking for. That is, iterate from start to end and stop when you find it.
As an aside, this is a great example of how a choice of data structure affects the availability of algorithms down the line. You can't just throw algorithms at a problem if you picked the wrong data structures in the first place!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With