Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs - caching updates #42857

Merged
merged 14 commits into from
Jun 4, 2024
Merged

docs - caching updates #42857

merged 14 commits into from
Jun 4, 2024

Conversation

jeff-bruemmer
Copy link
Member

Updates docs to reflect new caching controls.

@jeff-bruemmer jeff-bruemmer self-assigned this May 17, 2024
@jeff-bruemmer jeff-bruemmer added backport Automatically create PR on current release branch on merge Type:Documentation labels May 17, 2024
Copy link
Contributor

@luizarakaki luizarakaki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Added a few comments


Your Metabase instance keeps track of how long it takes each question to run. The average query execution time is used in your [caching settings](#caching-settings).
Pick when to regularly invalidate the cache. Metabase will periodically run the query according to the schedule you set and store the results. Other people running queries have no effect on when the results are refreshed; they'll always get the cached results unless they explicitly [clear the cache](#clearing-the-cache).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Metabase doesn't periodically run queries.

We periodically invalidate the cache.
If it is scheduled to invalidate the cache every 6h starting midnight, we will invalidate the cache (if it exists) at 0, 6, 12, and 18.

If no one runs the query in this interval, there won't be any cache and nothing will be invalidated.
Also, the query will run at least once in the interval (to create the cache)


You can tell Metabase when and what to cache from **Admin settings** > **Caching**:
We do not yet support lunar cycles.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol

docs/configuring-metabase/caching.md Show resolved Hide resolved
docs/configuring-metabase/caching.md Outdated Show resolved Hide resolved
docs/configuring-metabase/caching.md Outdated Show resolved Hide resolved
@jeff-bruemmer jeff-bruemmer merged commit d9aaa9f into master Jun 4, 2024
108 checks passed
@jeff-bruemmer jeff-bruemmer deleted the docs-perf-caching branch June 4, 2024 17:25
Copy link

github-actions bot commented Jun 4, 2024

@jeff-bruemmer Did you forget to add a milestone to the issue for this PR? When and where should I add a milestone?

github-automation-metabase pushed a commit that referenced this pull request Jun 4, 2024
jeff-bruemmer added a commit that referenced this pull request Jun 5, 2024
Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>
@sloansparger sloansparger added this to the 0.50 milestone Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Automatically create PR on current release branch on merge Type:Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants