First Load of a Record
To provide the best customer experience, NetSuite leverages multilayer caching to speed up performance on frequently used operations. For the first execution of a record and action combination (for example, viewing a sales order), the system needs more time to load and perform the action. For subsequent executions, the cached portions of the operation will perform faster than the first execution. Actions that are not frequently used may be removed from a cache over time and take longer to execute on the next, uncached execution. This performance impact is known as first-load latency.
Any of the following operations can cause actions to be removed from a cache and may cause users to experience first-load latency:
-
Logging into NetSuite (this action establishes a user’s first cache for a session)
-
Changing roles or altering permissions
-
Enabling or disabling account features or user preferences
-
Clearing a browser cache of images, data, or cookies
-
Using the system infrequently (stale data is flushed from a cache automatically)
First Load Considerations
The multilayer caching mechanism in NetSuite is optimized for the most-used records and actions, and it cannot be adjusted by customers. However, users with the Administrator role can customize roles with permissions and access levels that limit the need for role switching, which can indirectly reduce system latency.
Some record and operation combinations, such as saving a sales order, can take different amounts of time to complete for different roles. You should make sure that you are using the appropriate role for the task you want to complete. The Administrator role includes most privileges that can be assigned to a role; therefore, the loading times for some operations could be longer for the Administrator role than they are for other roles with fewer privileges. If another role can accomplish the task, using the role with fewer permissions may improve loading times.