Skip to content

Commit 6ea1d0f

Browse files
Update caching.mdx (#7759)
Rewording caching types, especially clarifying in-memory cache
1 parent 546086f commit 6ea1d0f

File tree

1 file changed

+17
-12
lines changed

1 file changed

+17
-12
lines changed

docs/pages/product/caching.mdx

Lines changed: 17 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -257,21 +257,26 @@ versions.
257257

258258
Any query that is fulfilled by Cube will use one of the following cache types:
259259

260-
- **[Pre-aggregations](#pre-aggregations) in Cube Store.** This is the most
261-
advantageous and performant option.
260+
- **[Pre-aggregations](#pre-aggregations) in Cube Store.** This cache type
261+
indicates that the query utilized existing pre-aggregations in Cube Store,
262+
so it did not need to go to the database for processing.
262263
- **Pre-aggregations in Cube Store with a suboptimal query plan.** This cache
263-
type indicates that queries still benefit from pre-aggregations in Cube Store
264-
but it's possible to get a performance boost by [using indexes][ref-indexes].
264+
type indicates that the query ultilized pre-aggregations in Cube Store,
265+
but that it's possible to get a performance boost by [using indexes][ref-indexes].
265266
- **Pre-aggregations in the data source.** This cache type indicates that
266-
queries don't benefit from pre-aggregations in Cube Store and it's possible
267-
to get a massive performance boost by using Cube Store as [pre-aggregation
267+
the query utilized pre-aggregations from in the upstream data source.
268+
These queries could gain a performance boost by using Cube Store as [pre-aggregation
268269
storage][ref-storage].
269-
- **[In-memory cache.](#in-memory-cache)** This cache type indicates that
270-
queries don't benefit from pre-aggregations at all. Queries directly hit the
271-
upstream data source and in-memory cache is used to speed up the execution of
272-
identical queries that arrive within a short period of time.
273-
- **No cache.** This cache type indicates queries that directly hit the
274-
upstream data source and have the worst performance possible.
270+
- **[In-memory cache.](#in-memory-cache)** This cache type indicates that the
271+
results were retrieved from Cube's in-memory cache. All query results
272+
are stored in Cube's in-memory cache, and if the same query is
273+
run within a certain time frame, the results will be retrieved from in-memory
274+
cache instead of being processed on the database or in Cube Store. This is the
275+
fastest query retrieval method, but it requires that the exact same query was
276+
run very recently.
277+
- **No cache.** This cache type indicates that the query was processed in the upstream
278+
data source and was not accelrated using pre-aggregations. These queries could have
279+
a significant performance boost if pre-aggregations and Cube Store were utilized.
275280

276281
In [Query History][ref-query-history] and throughout Cube Cloud, colored bolt
277282
icons are used to indicate the cache type. Also, [Performance

0 commit comments

Comments
 (0)