Try our conversational search powered by Generative AI!

Cache invalidation takes up to 5 min


We have one epi-installation for the editors; this server publishes the information and distributes it to three front slaves.

They all share the same database.

We have set up the cache invalidation using tcp/ip according to the guidelines and it works.

However we have noticed that the invalidation time varies up to five minutes for a random node.

This is not a acceptable time and the customer wants a instant page update on all the front slave nodes.

Have any one had any similar problems?


Apr 07, 2011 12:58
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.