The

module for Drupal 8 stores the Purge status in a key_value pair. On a busy site with many content updates, this can create performance problems. Avoid single table rows when you need to keep track of a large amount of data.

The table below provides an example of how the key_value size compares with other tables on the same site:

The

module for Drupal 8 stores the Purge status in a key_value pair. On a busy site with many content updates, this can create performance problems. Avoid single table rows when you need to keep track of a large amount of data.

The table below provides an example of how the key_value size compares with other tables on the same site:

For an alternate design, visit the Drupal Migration Center.

Acquia recommends the following:

1. Deactivate the Akamai module.

2. Use the Purge and Acquia Purge module.

3. When you use the Purge and Acquia Purge modules, Cache tag-based content purging is enabled on your Content Management System (CMS).

4. These work well with Content Delivery Networks (CDN) like Akamai.

5. Set the Edge Cache Time To Live (TTL) low and set the time between 1 minute and 5 minutes, depending on your application requirements.

6. Set the Browser Cache TTL to 1 minute, or the same value as Edge Cache TTL.

Occasionally, an application can require a shorter Edge Cache TTL lifetime. If you reduce the amount of your Edge Cache TTL, ensure that you change the Browser Cache TTL to the same value.

After you configure the module properly, the Acquia Purge module causes content updates to purge selected portions of Varnish cache. The next time Acquia Cloud Edge CDN requests the content from Varnish, it receives the updated content.

If you must have the Akamai module installed, set the Purge Status expiry to 0 in the purge settings at admin > config > akamai > config.

This issue may have been resolved recently. Visit Akamai Drupal Module issue resolution for details.