It appears the Drupal layer of caching is not necessary now that the sitemap index is also stored in the database as opposed to being generated on the fly. There are just a few database calls on every sitemap view which seems to have little impact. This is just theoretical, as I have not measured the performance hit of calling the sitemap without caching as opposed to the cached variant.

If anyone wants to do some testing and support the idea of caching the 3.x version of the module, I am willing to look at the data and possibly reimplement caching.

Comments

gbyte.co created an issue. See original summary.

gbyte’s picture

Issue summary: View changes

  • gbyte.co committed 2c8224c on 8.x-3.x
    Issue #3001470 by gbyte.co: Remove caching as now all sitemap content is...
gbyte’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.