Home » Blogs » jwheat's blog

Targeted Content Caching?

Submitted by jwheat on Thu, 2010-06-03 11:38

We're doing some heavy content channel work with TCC, and its a complete unreasonable situation that I have to wait for the content to update. It takes 10-20 minutes before the content change is reflected in the channel.

Any idea the configman setting to change? At this point I don't care about the performance hit.

-Jon

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Test Settings

Submitted by mrose on Thu, 2010-06-03 12:08.

Hey Jon,

In our test environment we use the following settings. This effectively turns off TCC caching.

TargetedContentChannel.cache.expiration = 1
content.cache.expire = 1
content.channel.cache.expire = 1

--mike

TargetedContentChannel.cache.expiration

Submitted by julied on Thu, 2010-06-03 12:19.

That's what I changed for our training:

The TargetedContentChannel.cache.expiration setting determines the cache expiration time for TCCs only. The value is set in seconds and the default is 900 (= 15 minutes). Usually during training and channel development we reduce it to 1

shotgun

Submitted by ToddTrann on Thu, 2010-06-03 12:16.

Somewhere in one of these?

content.cache.expire
content.cache.size
content.cache.timeout
content.category.cache.expire
content.category.cache.size
content.channel.cache.expire
content.channel.cache.size

TCC cache - got it !

Submitted by jwheat on Thu, 2010-06-03 15:12.

Thanks.

ended up being this one :
TargetedContentChannel.cache.expiration = 1

yea, much happier now.
-Jon

Syndicate content