I understand the pages are cached for anonymous users, but not for logged in users.
My tag pages take 2 to 9 (!) seconds to be computed, which is much too much... (it's ok now that my site has few users, but I can't imagine drupal.org using this module!).
Instead of being updated at each page view, can a cron job be setup to create a few selected tag pages (or blocks), and the result being always retrieved from the cache for everybody?
For example, I have:
http://www.wechange.org/tagadelic
which is not aliased, but also:
http://www.wechange.org/tagadelic/places which is /tagadelic/chunk/5
etc.
And I may want to have tagadelic/chunk/5,8 but not tagadelic/chunk/2 so it would be useful to be able to configure which pages are to be computed by the cron job or not.
I'm still unsure how the cache systems works within Drupal.
Comments
Comment #1
Bèr Kessels commentedNo need for cron. We should cache the arrays with weighted objects instead. There is even a comment in the code on the place where this should happen.
Comment #2
Bèr Kessels commentedAlso. I don't introduce new features on a stable branch. Moving this issue to CVS/HEAD.
Comment #3
Bèr Kessels commentedCorrected the title
Comment #4
Bèr Kessels commentedhttp://drupal.org/node/78573