Group Cache Invalidation for Improve...

TL;DR Opening

Group cache invalidation is a powerful feature in NetSuite that reduces individual cache invalidation requests, thereby enhancing system performance, especially when handling file uploads and SOAP web services.

What is Group Cache Invalidation?

Group cache invalidation allows multiple cache invalidation requests to be processed as a single request under certain conditions. This is particularly useful when users upload files to the File Cabinet, as it minimizes the overhead associated with handling numerous individual requests.

When Does Group Cache Invalidation Occur?

Group invalidation requests are generated in the following scenarios:

SOAP Web Services: When files are uploaded using SOAP web services to the File Cabinet.
File Uploads: When a .zip file is uploaded to the File Cabinet. In this case, if multiple path invalidation requests reach a certain threshold, they may be replaced with a single wildcard invalidation request.

Understanding Cache Invalidation Requests

All cache invalidation requests that are part of a group share the same timestamp. Administrators can monitor these requests on the Cache Invalidation Status page, providing visibility on system activity.

Automatic Throttling of Requests

To enhance performance, NetSuite employs automatic throttling for cache invalidation requests. This is critical to prevent the generation of an excessive number of requests, which could overwhelm the system. For example, certain scheduled scripts that modify files may trigger numerous cache invalidation requests. In such cases, the cache invalidation requests are created but may be disabled due to throttling, resulting in a Suspended status on the Cache Invalidation Status page.

By leveraging group cache invalidation and automatic throttling, NetSuite aims to provide a smoother user experience while maintaining optimal system performance.

Who This Affects

Administrators responsible for managing system performance.
Developers using SOAP web services or uploading files.
Users uploading large volumes of files to the File Cabinet.

Key Takeaways

Group cache invalidation consolidates multiple requests for improved performance.
Triggered primarily by file uploads and SOAP web services.
Automatic throttling prevents excessive cache invalidation requests.
Requests within a group share the same timestamp, facilitating easier monitoring.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

Does group cache invalidation apply to both WMS and standard NetSuite?

The article does not specify if group cache invalidation applies to WMS. It focuses on standard NetSuite features like file uploads to the File Cabinet and SOAP web services.

Is there a threshold for converting multiple path invalidations to a single wildcard invalidation?

Yes, when uploading a .zip file to the File Cabinet, if multiple path invalidation requests reach a certain threshold, they may be converted into a single wildcard invalidation request.

What happens to cache invalidation requests if they trigger throttling?

If throttling is triggered, the cache invalidation requests may be automatically disabled, leading to a Suspended status on the Cache Invalidation Status page to prevent system overwhelm.

Can administrators monitor which cache invalidation requests have been grouped?

Yes, administrators can monitor grouped cache invalidation requests on the Cache Invalidation Status page, where all requests in a group will display the same timestamp for tracking purposes.

Group Cache Invalidation for Improved Performance in NetSuite