Caching projection part result

Topics: Customizing Orchard, Troubleshooting, Writing modules
Jul 18, 2012 at 12:49 PM
Edited Jul 18, 2012 at 1:30 PM

Anyone knows what I need to do to cache the output of a projection part?


I made the part attachable, created a custom content type with it, and it all works nicely.

But the page takes 1 second to render (the rest is ~100-200ms) and I fear our client will dislike this performance.

I know that (per culture at least) the rendered result of the projection will not 'dynamically' change (until ofc one of the 'contents' is changed)

So, anyone got a clue? I'm aware about the caching module, but that only acts if people aren't logged in (and on our site they could be logged in)

edit: Or as an alternative / addition, would it be possible to cache the output of a certain zone? Some pointers would be helpful :)

Jul 23, 2012 at 11:08 AM

This may be helpful:

Jul 24, 2012 at 5:40 AM

Thanks for that! :)