I'm doing some performance tuning on a complex content, high traffic view and I couldn't find any documentation on the precise difference between the two settings for time based caching - query results and rendered output. Apologies if this documentation exists and I failed to find it.

Comments

thomasmurphy created an issue. See original summary.

MustangGB’s picture

MustangGB CreditAttribution: MustangGB commented

Difference in output or difference in performance?

AFAIK there is no difference in output, besides the obvious that the results won't be updated until the cache is expired.

Regarding performance it obviously depends on how slow the original query was, but cached results are generally orders of magnitude faster if your query was somewhat complex with several joins.

thomasmurphy’s picture

thomasmurphy CreditAttribution: thomasmurphy as a volunteer commented

This is more of an documentation request on how the module actually works. I'm currently guessing that there is a table which matches query strings to rendered markup, but I actually have no idea how views caching works. If I did understand it I'm presuming that I could use views caching more effectively.

MustangGB’s picture

MustangGB CreditAttribution: MustangGB commented
Status: Active » Closed (outdated)

Closing this as outdated to tidy up a bit around here. If you're still having problems with the latest release please create a new issue.