Manage and optimize usage for Incremental Static Regeneration

The Incremental Static Regeneration section shows the following charts:

ISR reads and writes are measured in 8 KB units:

• Read unit: One read unit equals 8 KB of data read from the ISR cache
• Write unit: One write unit equals 8 KB of data written to the ISR cache

ISR Reads and Writes are priced regionally based on the location of the request. See the regional pricing documentation for more information.

You are charged based on the volume of data read from and written to the ISR cache, and the regions where reads and writes occur. To optimize ISR usage, consider the following strategies.

• For content that rarely changes, set a longer time-based revalidation interval
• If you have events that trigger data updates, use on-demand revalidation

When attempting to perform a revalidation, if the content has no changes from the previous version, no ISR write units will be incurred. This applies to be time-based ISR as well as on-demand revalidation.

If you are seeing writes, this is because the content has changed. Here's how you can debug unexpected writes:

• Ensure you're not using new Date() in the ISR output
• Ensure you're not using Math.random() in the ISR output
• Ensure any other code which produces a non-deterministic output is not included in the ISR output

You get charged based on the amount of data read from your ISR cache and the region(s) in which the reads happen.

When viewing your ISR read units chart, you can group by:

• Projects: To see the number of read units for each project
• Region: To see the number of read units for each region

You get charged based on the amount of ISR write units written to your ISR cache and the region(s) in which the writes happen.

When viewing your ISR writes chart, you can group by sum of units to see a total of all writes across your team's projects.

• Projects: To see the number of write units for each project
• Region: To see the number of write units for each region