Oracle Analytics and AI

Rajakumar Burra

When we load workbook, only active canvas is loading.

When we switch to next canvas , it is taking time to load the canvas.

It is becoming embarassing situation to wait till load the canvas during meetings and presentations.

If I have 5 canvases in one workbook, if I activate 5 once and come back to 1st sheet, remaining sheets loading in background.

Actually it should be loaded background without activating the data.

Gabby Rubin-Oracle

Loading only active/touched canvases is intentional:

1. Extensive load on the system that will impact concurrency. The increase in query load on the system will be significant as every user will process multiple queries they will never view/use. The impact on the sizing of environments (both OAC and data sources) will increase customer costs, which is why customers usually ask to avoid unnecessary workloads.
2. Dependencies such as shared filters will require the pre-loaded canvases to reload (at filter change or on navigation), making the pre-load a wasted effort.
3. The assumption is that the time taken is query time (a valid assumption in most cases), but rendering might also take time in some cases and cannot be done in the background.

The solution for a specific meeting is simple: ahead of the meeting, navigate to each canvas and trigger the canvas load. Once done, the system will use the pre-loaded version (unless filters are changed). Based on your comment, you might already be doing it (?). There are other more advanced options to pre-seed the cache, but this is the simplest for an interactive user.