Oracle Communities

Oracle Analytics and AI

Child Item

Need a way to seed the cache for OAS DV Dashboard

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

LCRA

Description (Required): We need a way to seed the cache for an OAS DV Dashboard. This can be similar to the BI Agent job used to cache Classic BI Dashboard or analysis.

Use Case and Business Need (Required): Needed to improve the performance of DV Dashboard.

Enhancement Request / Service Request:

Find more posts tagged with

Delivered

Reporting

Analysis and Data Visualization

Status: Delivered

Comments

Gabby Rubin-Oracle

OAC 6.0 introduced the ability to schedule the refresh of cached datasets. It will come to OAS in the next feature release.

Kevin T

Will the OAC 6.0 cache DV projects too?

Bret Grinslade - Oracle Analytics-Oracle

Not exactly. Projects use queries which can be to datasets Live queries or automatic caching. If automatic caching is used, you can schedule these to ensure you have data at a specific time such as 6am or hourly for example. Projects when they load will query the source or cache. If the source system is slow, Automatic caching with a scheduled reload may give you better performance.

Angel Shipp

@Gabby Rubin-Oracle , you mentioned ability to schedule or refresh cached datasets in 6.0. This limits caching to DV projects that use data sets only, correct? What about the DV Projects that use Subject Areas? It would be ideal if we are able to seed/cache all types of DV projects for better performance and customer experience.

Kevin T

@Gabby Rubin-Oracle yes, I'm also curious about that too because we use subjects areas for now. That would be great if we can cache seed the DV projects that use subject areas.

JasonJang-Oracle

@Kevin T , "That would be great if we can cache seed the DV projects that use subject areas." —> Does it mean that There is no way to seed cache in DV using Subject Area now for OAC ? , we need this. also

Gabby Rubin-Oracle

Cache can mean multiple things.

Query cache—available for live queries, regardless of Datasets or Subject Areas. Basically, cache query results are in memory and generally managed as FIFO based on the cache size. Seeding usually means having a process that will execute the queries in close proximity to the users' usage.
Datasets that are not based on live queries to the external source system but load the data into the OAC/OAS internal store are referred to as cached Datasets. Unlike the memory-based query cache, this is a storage-based cache that is controlled by the user (the user controls when the data is refreshed), and the system never removes it from the storage.