We are running a large website that uses extensive caching (using MemCacheD)
On publish, we intercept the AfterPublish event to clear out these caches and rebuild the various data structures that reside therein.
The problem is, when publishing occurs in batch (say, when the home page and all children are published in one shot) our cache reload fires for every document in that batch, causing terrible performance and often causing a script timeout.
Does anyone know a good way for us to detect when the batch publish has completed so that we could do our cache rebuild at that point?
best way to handle non-repeating publish events on batch publishes?
We are running a large website that uses extensive caching (using MemCacheD)
On publish, we intercept the AfterPublish event to clear out these caches and rebuild the various data structures that reside therein.
The problem is, when publishing occurs in batch (say, when the home page and all children are published in one shot) our cache reload fires for every document in that batch, causing terrible performance and often causing a script timeout.
Does anyone know a good way for us to detect when the batch publish has completed so that we could do our cache rebuild at that point?
nobody? (top)
I'd be inerested in how to do this too. I'd also be interested in what the AfterPublish event looks like that blocks the cache rebuild.
is working on a reply...