Skip to content
This repository has been archived by the owner on Jul 26, 2024. It is now read-only.

Introduce initial randomized cache TTL for tiles #261

Closed
jrconlin opened this issue Aug 12, 2021 · 2 comments
Closed

Introduce initial randomized cache TTL for tiles #261

jrconlin opened this issue Aug 12, 2021 · 2 comments
Labels
3 3 Estimate - m - This is a small change, but there's some uncertainty. enhancement New feature or request

Comments

@jrconlin
Copy link
Member

jrconlin commented Aug 12, 2021

With the use of the "jitter" we still get initial "waves" of requests due to the jitter only adjusting time at the end of a cache fetch.
image

Instead, we should use an initial random time that is between 0+jitter to ttl-jitter for initial tile entries. This should cause the wave to be dampened faster since TTLs would already be fairly well distributed.

┆Issue is synchronized with this Jira Task

@jrconlin jrconlin added enhancement New feature or request 3 3 Estimate - m - This is a small change, but there's some uncertainty. labels Aug 12, 2021
@data-sync-user
Copy link
Collaborator

➤ JR Conlin commented:

Closed by #221 ( https://github.com/mozilla-services/contile/pull/221|smart-link )

@jrconlin
Copy link
Member Author

A few reasons why this was closed:

  1. We still need to hit ADM's cache to get data (until there's a shared cache), and delaying that just means that things down stream hang for no good reason.
  2. the peaks level out fairly quickly, so it's less of a concern than I initially thought it was.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3 3 Estimate - m - This is a small change, but there's some uncertainty. enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants