zydronium/google-nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus.git synced 2025-05-14 16:37:13 +02:00
Code Issues Projects Releases Packages Wiki Activity

Clarify what affects the size of the premium list entry cache

Browse source 
-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=149680785
This commit is contained in:
mcilwain 2017-03-09 12:19:41 -08:00 • committed by Ben McIlwain
parent 3b2a014524
commit fa5d23bc19
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
java/google/registry/model/registry/label/PremiumList.java
View file

@ -178,8 +178,9 @@ public final class PremiumList extends BaseDomainLabelList<Money, PremiumList.Pr
* changed once created, so the cache need not ever expire. * changed once created, so the cache need not ever expire.
* *
* <p>A maximum size is set here on the cache because it can potentially grow too big to fit in * <p>A maximum size is set here on the cache because it can potentially grow too big to fit in
* memory if there are a very large number of premium list entries in the system. The least- * memory if there are a large number of distinct premium list entries being queried (both those
* accessed entries will be evicted first. * that exist, as well as those that might exist according to the bloom filter, must be cached).
* The entries judged least likely to be accessed again will be evicted first.
*/ */
@VisibleForTesting @VisibleForTesting
static final LoadingCache<Key<PremiumListEntry>, Optional<PremiumListEntry>> static final LoadingCache<Key<PremiumListEntry>, Optional<PremiumListEntry>>