3 ms·
This is a very bad example, but the underlying concepts are useful. It's more realistic if you are storing a set of revoked access keys or altered files on you
by marcosdumay 5y ago
This is a very bad example, but the underlying concepts are useful.
It's more realistic if you are storing a set of revoked access keys or altered files on your cache that you subscribe from some channel that is not on your main request - database - response loop.
Normally you won't ever need to store many of those until they reach the expiration time or you update you cache, and you will want a lot of performance for the common case (what the small memory requirements help ensuring).
- marginalia_nu 5y agoI think fundamentally bloom filters are mainly useful for astronomical data sizes. If you have a petabyte of data partitioned between several datacenters, and you want to know which shards have entries with certain properties, bloom filers are amazing. A bloom filter that is just a few dozen megabytes can save you an enormous amount of computation in such a scenario. To cache network requests it really isn't that great. A basic LRU cache typically performs just as good, and is a lot easier to get right.