From fa5d23bc1946bcec3263a19303b7f75cd34e403f Mon Sep 17 00:00:00 2001
From: mcilwain <mcilwain@google.com>
Date: Thu, 9 Mar 2017 12:19:41 -0800
Subject: [PATCH] Clarify what affects the size of the premium list entry cache

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=149680785
---
 java/google/registry/model/registry/label/PremiumList.java | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/java/google/registry/model/registry/label/PremiumList.java b/java/google/registry/model/registry/label/PremiumList.java
index 9fdc7d7c4..767111d6b 100644
--- a/java/google/registry/model/registry/label/PremiumList.java
+++ b/java/google/registry/model/registry/label/PremiumList.java
@@ -178,8 +178,9 @@ public final class PremiumList extends BaseDomainLabelList<Money, PremiumList.Pr
    * 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
-   * memory if there are a very large number of premium list entries in the system. The least-
-   * accessed entries will be evicted first.
+   * memory if there are a large number of distinct premium list entries being queried (both those
+   * 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
   static final LoadingCache<Key<PremiumListEntry>, Optional<PremiumListEntry>>