Manage and optimize usage for Edge Config

The Edge Config section shows the following charts:

• Keep the number of stores to a minimum. Fewer large stores improves your overall latency

The Reads chart shows the number of times your Edge Config has been read. You can filter the data by Count or Projects.

• Select the Project tab to identify which project has the most Edge Config reads
• Review how you access the stores through both the REST API and the SDK. They both count toward your reads
• Where possible, use getAll() instead of separate get(key) calls with the SDK, so that they count as a single read

The Writes chart shows the number of times your Edge Configs were updated. You can filter the data by Count or Edge Configs.

• Select the Edge Configs tab to identify which Edge Config has the most Edge Config writes
• Review your points of updating the stores through the REST API as they count towards your writes