Prevent Hive Pages from Loading on Every View

Prevent Hive Pages from Loading on Every View

Question

There is a Hive page that currently has multiple embedded visualizations from different platforms. When the user first accesses the page, the visuals are loaded, which is to be expected. If the user navigates to another page within the Hive, and then they return to the previous page, all the visualizations are executed again. This is inconvenient for the user as they have to wait, sometimes it's quite a long wait for some platforms, affects audit statistics, and causes extra load on the BI systems.



Is there a way to prevent the visualizations from executing every time that a page is viewed?

Answer

As of the Digital Hive 2024.1 release, it is possible to configure a Hive page so that the page contents are executed when the page is first accessed, and then remain in memory for subsequent page views.

  1. Open the Hive Designer to edit the desired Hive
  2. Open the Properties  panel
  3. Using the Page selector  drop-down, select the desired page
  4. Scroll down the Properties panel and locate the Performance section
  5. Expand the Performance section using the down  chevron
  6. Enable the Keep page loaded option
     
  7. Save the changes to the Hive 
These changes will now cause the page to stay loaded into memory if a user navigates to another page in the SAME Hive, and then back to the original page. If the user navigates to a different Hive, and then back to the original Hive and page, the page will reload. The page only remains in memory while a single Hive is being explored. 

This video demonstrates the experience before the Keep page loaded setting is enabled, how to enable the setting, and then what the new user experience is with the page remaining in memory.



Enabling this setting should not be done on every page, only the ones that contain embedded visualizations that take time to render and that users may visit multiple times during a session. With this setting enabled, each page that is configured to stay loaded in memory will consume browser memory. This may not be an issue for some users, but others that tend to keep a large amount of browser tabs open may be affected.