Please apply a random fuzz to cache expiration. It will remove any chance of 30 day interval load clumping and ensure that our clients are instead fully spread out amongst the available time.
I recommend doing this by adding a random 1-86400 seconds to the expiration constant at code startup time. That way each instance will start up with a slightly different expiration constant, and it's completely acceptable if that constant changes after each restart, since it's the difference between 30 and 31 days of country code caching, which is irrelevant.
If exceeding the 30 day boundary is unsatisfactory, lower the base constant to 29.0 (or 29.5) days, so that the fuzz covers 29.0-30.0 days (or 29.5-30.5 days).
Please apply a random fuzz to cache expiration. It will remove any chance of 30 day interval load clumping and ensure that our clients are instead fully spread out amongst the available time.
I recommend doing this by adding a random 1-86400 seconds to the expiration constant at code startup time. That way each instance will start up with a slightly different expiration constant, and it's completely acceptable if that constant changes after each restart, since it's the difference between 30 and 31 days of country code caching, which is irrelevant.
If exceeding the 30 day boundary is unsatisfactory, lower the base constant to 29.0 (or 29.5) days, so that the fuzz covers 29.0-30.0 days (or 29.5-30.5 days).