Just wondering what are the best options for date caching?

From other sites that I have worked with, this can be an important factor as far as performance goes, especially when looking at a calendar View with many repeat dates.

In the case of repeating entities, I'm guessing that caching is not so important, but I would really appreciate some clarification.

Cache dates
Date objects can be created and cached as date fields are loaded rather than when they are displayed to improve performance.

Maximum dates per field: Default = 4

If set to '0', all date values on every entity will be cached. Note that caching every date on fields that may have a large number of multiple or repeating values may create a significant performance penalty when the cache is cleared. The suggested setting for multiple value and repeating fields is no more than 4 values per field.

Comments

mrpauldriver’s picture

mrpauldriver commented
Issue summary: View changes
eft’s picture

eft commented
Status: Active » Postponed (maintainer needs more info)

I have not explored the caching mechanism for recurring dates. Presumably, the different deltas (rows within the field table) are cached. In the case of this module those deltas are replaced by actual entities, as you indicated, so the limit on date caching becomes moot.

I would be interested in any anectodal data you can provide. Marking as postponed for now.