I would like to see backend caching performed and the display use the cached data to display the terms. Calculating at the time of display is killing my site and I've had to disable tagadelic blocks. 

{term_data}
vid 	count( * )
1 	12743
3 	167041
4 	12630
5 	11234
6 	9

{term_node}
count(*)
1858469

Comments

Anonymous’s picture

Anonymous (not verified) commented

I should have added that I envision the backend cache happening at the time node save. Yes, if this feature were enabled it would slow the save but my data is completely automated with very little user input.

Bèr Kessels’s picture

Bèr Kessels commented

As you admit: this will only help a few. Is the extra code and complexity worth that? Can we not look into a better caching, with intermediate cache systems and/or cron-based re-calulation?

Anonymous’s picture

Anonymous (not verified) commented

I can say that my use of tagadelic slowed my site enough that I had to disable the cloud blocks. As it exists today tagadelic isn't functioning well for large sets of tags. Caching at the time of DB change is the only way I know to have real time results. Caching from cron will only slow the cron run and cause other issues since I could add thousands (or more) of rows at once.

Bèr Kessels’s picture

Bèr Kessels commented

This makes sense.

Though looking at other parts of Core Drupal learns me that the "preferred way" is to do it on cron. See search indexing, filter-updates etc.

I prefer to go for (in that particular order)
* the simplest solution
* the solution that behaves most DRupalish
* the solution with least "options"
* the solution that benefits most of us

What do you think, would your case be solved with a cron-based one? Or are you only helped with an onChange solution?

Anonymous’s picture

Anonymous (not verified) commented

I don't know. It would depend on how long the process took. I'm thinking that it would help be helped. If you do add a cron then you need a variable for how many times in a 24 hour period to run it. I execute cron.php once every 5 minutes but wouldn't want to execute this that often.

Bèr Kessels’s picture

Bèr Kessels commented

For certain the cron interval zould be configurable. Most (if not all) cron-based-module have such a setting. Default to core cache refresh interval?

Anonymous’s picture

Anonymous (not verified) commented

Default to core cache refresh interval?

Yes, that works.

Bèr Kessels’s picture

Bèr Kessels commented
Status: Active » Fixed

AFAIK the current caching will suffice. Closing issue.

Status: Fixed » Closed (fixed)

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

jcisio’s picture

jcisio commented
Version: 6.x-1.x-dev » 6.x-1.2
Priority: Critical » Normal
Status: Closed (fixed) » Active

I reopen the issue because caching is not available in the last stable release (yet, two years ago). Will 6.x-1.3 be out soon?

Cache is suitable for large websites. For those, there are too many nodes and tagadelic data won't change rapidly. I don't know how ofter cache is cleared with CACHE_TEMPORARY, but it shouldn't be cleared often.

Bèr Kessels’s picture

Bèr Kessels commented
Status: Active » Closed (fixed)

please do not reopen. It really was fixed. Just no release yet.