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

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 reads and writes, consider the following strategies.

• For content that rarely changes, set a longer revalidation interval
• This minimizes the frequency of ISR writes

View a time-based revalidation example.

• If you have events that trigger data updates, use on-demand revalidation
• This will help you avoid unnecessary ISR writes

View a on-demand revalidation example.

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